9,310
edits
Resco JavaScript Bridge: Difference between revisions
Jump to navigation
Jump to search
→Web browser component
| Line 94: | Line 94: | ||
Another important aspect to consider is that when a page is displayed in Web Browser Component, some of the features might not be enabled. A typical example is Window.Print() – even though this function is supported by many mobile browsers, when the browsers are running in the Web Browser Component (i.e. in Resco mobile application) this feature is disabled. | Another important aspect to consider is that when a page is displayed in Web Browser Component, some of the features might not be enabled. A typical example is Window.Print() – even though this function is supported by many mobile browsers, when the browsers are running in the Web Browser Component (i.e. in Resco mobile application) this feature is disabled. | ||
<span class="plainlinks">From the list of unsupported features, it's worth to mention APIs that open some content in the new window or tab and [https://en.wikipedia.org/wiki/XMLHttpRequest XHR]/[https://en.wikipedia.org/wiki/Ajax_(programming) Ajax] requests requiring [https://en.wikipedia.org/wiki/Cross-origin_resource_sharing CORS]. All these APIs has to be replaced by Mobile CRM components supplying this functionality via JSBridge. </span> | |||
Unfortunately, there is no universal list of disabled features, commands, or tags – this differs from platform to platform, browser version, OS version, and so on. To be entirely sure, make sure you test the application and the custom content on all the devices. | Unfortunately, there is no universal list of disabled features, commands, or tags – this differs from platform to platform, browser version, OS version, and so on. To be entirely sure, make sure you test the application and the custom content on all the devices. | ||