This topic is 2461 days old. Please don't post here. Open a new topic instead.
This is a peculiar bug which seems to have appeared with a recent Chrome update.
Create a Web Viewer control with the following content:
"data:text/html,<html><body bgcolor=\"#EEEEEE\">HELLO</body></html>" Then view the layout in WebDirect in Chrome. You'll notice it doesn't display anything. Remove the bgcolor and it works as expected. It also works in FileMaker.
There are numerous workarounds but I can't find out how to fix it.
Anyone else experienced this?
By Jonathan Ackerman
I am developing an app where users may login with Android or IOS via Webdirect.
On IOS (safari) via Webdirect-- everything is fine.
With Android(chrome)-- anytime the script refreshes the screen or switches panels-- all uncommitted data is lost.
any ideas or workarounds?--
my script checks validation and i really need to refresh to trigger conditional formatting
also hoping to have a multi-panel entry so the user does not have to scroll to the bottom (layout has about 100 fields)
By Jonathan Ackerman
When using WebDirect on an Android phone- sometimes when switching to a newlayout (via a scripted button)--
all formatting disappears-
see attached images.
(also noticed that it also happens on webdirect via a desktop browser)
anyone have ideas?
with correct formatting:
all formatting suddenly missing:
We have a newly deployed OS X 10.10.5 Server with FMS14 installed with only 3 databases hosted, all accessible via Web Direct.
Now some of our customers are experiencing difficulties with even accessing our solutions, which we have narrowed down to local network problems at our customers.
The problem is, the login window is not showing, and therefore they can't access the databases.
I then tried to connect to the database through Chrome, which worked perfectly fine!
Is there something I can do for the customer or on our Server, to prevent this message for future customers?
By Jesper Søholm Biberkopf
First a disclaimer. I'm well aware that WebDirect (FM13) is not build or supported for iOS or Android tablets. I've read the specifications. And yes, things should probably be done in PHP instead. Which is no doubt, what will happen eventually. But for a number of reasons, I'm involved in a couple of projects, where we have decided to examine the borders of WebDirects compatibilty first.
So I would like to hear any concrete findings from other crazy persons who have been experimenting on the wild side with WebDirect. What kind of functions and design methods work for you. What should we avoid in striving for a solution to best survive in e.g. Chrome on an Android tablet? Any experiences with Raspberry?
Why is this interesting? Well, unless you publish your WebDirect solution on an intranet or another very controlled environment, there will always be users who will try to use whatever browser is at hand. So we might as well prepare and try to recognize and understand the things that can and will go wrong in those situations. Maybe we might even collect some useful feedback for the good developers at FMI. ;-)
Who Viewed the Topic