The issue: Since web viewers in 19.3 flush cookies and storage when the file is closed, DayBack’s “ remember me” option no longer works when you sign into the file. Users will be asked to log into DayBack each time However, since 19.3 web viewers on Windows don’t retain local storage or cookies beyond the current session, DayBack users will notice two changes. ![]() We rewrote the calendar to take advantage of FileMaker 19’s new JavaScript functions, including FileMaker.PerformScript, instead of relying on fmp:// URLs. Since most of the breaking changes involve fmp:// URLs, DayBack for FileMaker 19 is largely unaffected. DayBack Classic uses callbacks to limit the number of times the whole web viewer needs to refresh–helping keep users focussed without “unscrolling” them, and making DayBack Classic feel more like a native part of FileMaker. 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).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |