This means that while web viewers can still run FileMaker scripts using fmp:// URLs when they are associated with links and buttons, web viewers can no longer run FileMaker scripts in most JavaScript callbacks. It’s not exactly clear what “rendering the layout” consists of, as URLs can execute when setting the web viewer from a script trigger or the web viewer content being loaded directly in the object itself. The result of this behavior is fmp:// URLs don’t need to be executed from a click action if the web viewer is being set when rendering the layout. New browser security rules in Windows prevent an fmp:// URL from being called when not initiated from a user action like a “click.” There seems to be an exception for this when the web viewer’s layout loads.And apps that use local storage or cookies to store the user’s state or tokens connecting to APIs, won’t be able to retain those facts after the FileMaker file is closed. In some cases, users may not even see the dialog asking for permission, and it may appear that the web viewer has hung up. The upshot of these two changes is that your users may be asked to OK each time a web viewer wants to run a FileMaker script. It appears these settings are scoped to the file’s session. Even if FileMaker is still running, it won’t retain those saved settings once the file is closed. This includes local storage, cookies, and selections to “always allow” the site to open FileMaker (described above). Web viewers in Windows clear all settings associated with the site when their FileMaker file closes.If you’re running into this in your own files, you can tweak the registry to grant access without a prompt.When referencing external files in the web viewer, the permission dialog is accompanied by an option to “always allow.” If referencing local files, permission is for “file://.” Otherwise, it will be for the URL referenced.When using a data-URL based web viewer, the permission dialog will appear every time the web viewer loads. Permission is for “localfm.assets.”.All fmp:// calls on Windows now show a dialog asking for permission to allow the site to open FileMaker Pro.
Here are the breaking changes we’ve been able to identify so far: However, it comes with a few behavior changes that can break some web viewer apps.
(That’s why these changes don’t affect Mac clients or folks who only have a Windows Server.) This is an excellent change overall and a big improvement over Internet Explorer.
0 kommentar(er)
