Since it's the result of the content providers blocking the content and not filemaker, I'm not sure that filemaker CAN do anything in future releases.
Given that WebDirect is already in the browser, I've just been using Open URL script step to open up maps in a separate tab/window, and not try to embed it directly in my apps. This maximizes compatibility, and most mapping systems support url based parameters for addresses or coordinates.
Open URL will just take you to the browser. How about If we would like to display the webpage in our filmmaker application.
How would I display google maps next to customer detail in webdirect. Is that even possible?
2 of 2 people found this helpful
When a webviewer is displayed in webDirect it is an rendered as an iFrame. All the web browsers handle iFrames differently.
The main issues that you will run into are associated with the restrictions that Google places on the display of content in iFrames. Google's API's all have different behaviours for iFrames, some are OK with them, others will not work. I think that paying Google helps, in other words, developer license can do things that the free version doesn't.
Yep, using WebViewers in WebDirect has become virtually impossible to get to work properly in lots of cases.... I recently even tried to display a basic html page hosted on the FileMaker Server itself and it wouldn't display in WebDirect, although it was fine in FileMaker Pro, and the same page opened fine when opened directly in a browser...
For the record, I'm having the opposite experience. I find web viewer is incredibly easy to use and to implement.
You'll need to check out what jbrown is doing with them. It's pretty spunky. http://www.soliantconsulting.com/soliant-tv/2016/12/web-viewer-integrations-library-playlist
I agree - WebViewers are great and so very useful and work well when used in FileMaker Pro and FileMaker Go - it's just when they are used in WebDirect things become difficult - there seems to be barely any external web content, pages or sites that successfully load into it, due to security restrictions to do with iFrames....