As far as I know, no browser can access a local file system without a dialog box (this for security reason).
so, as for me it is the right behaviour.
to acces the image, it should reside on the server
1 of 1 people found this helpful
a very useful hint by monkeybreadsoftware with another issue:
"Please be aware that FM16 switches to WebKit 2.x instead of WebKit 1.x in FM15.
This change has a lot of side effects as you have a different browser engine there!"
What do you mean with "reside on the server"? In my example, the picture resides just next to the FM-file, I never had a problem open a local website-structure in safari nor do I with the current macOS.
The pcture "file:///"-path entered in Safari displays it flawless....
sorry, I misundestood your post
Wel there absolutely is some specific behaviour with the use of single and double quotes in the html around elementvalues in the webviewer.
I moved my local file online.
This works: <div id='text' style='position: absolute; top: 0; left: 0; width: 100%; background: url(\"http://your_url_to_your_file_or_image.png\") repeat-x ; '>
This doesn't: <div id='text' style='position: absolute; top: 0; left: 0; width: 100%; background: url('http://your_url_to_your_file_or_image.png') repeat-x ; '>
FM16 advanced, macOS Sierra
Hope you can tryout combinations and find your workaround.
The url is within the style. Nested quotes!
Sent from miPhone
I can replicate this issue.
The point is it's just a bug or a intentional change relating security.
Does anyone know the comment about this issue by FileMaker.Inc?
If you export the image to the temporary path, you can show it.It seems that accessable area of local files is limited in ver16.
2 of 2 people found this helpful
thanks for testing. there's no answer from fmi yet. It might have to do with webkit2 restrictions, as it still works on the windows version.
I can definitely replicate the issue under macOS Sierra 10.12.4. I have sent your posts, along with your sample files, to our Development and Testing departments for review. When I receive any feedback, I will let you know.
My apologies for the late reply.
Our Development and Testing departments are already aware of this issue. Your post has been attached to the original report. When more information becomes available, I will post again.