Hi
I have the following simple html code in a webviewer that displays a pdf with some simple javascript that scrolls the pdf. THis all works great on FMP but on Filemaker GO the webviewer is blank. Can anyone shed some light on this as to how i can solve this problem.
Attached is screenshot of HTML as pasting here deletes some lines
Hi thanks. Yes i am using the get (temporaryPath ) function to create the path. The path works fine and displays the pdf fine on GO if i do not use the javascript code. I will try send screenshot of webviewer html for GO just for clarity
Hi,
I think access to local files from web viewer( data-scheme ) is restricted.
How about exporting your html file with pdf to the temporary path?
Then set the path to the html file in the web viewer.
Hi Sam
Thanks for the reply. Yes currently the pdf sits in a container. On GO it is exported to temporary directory and Web Viewer is set with below code. PDF display fine in the WV if it is just the file path but when i add the below html code and java script the pdf does not display. However the below code works fine on FMP no problems. Attached also show the $$PATH variable calculation
List(
"data:text/html," ;
"<!DOCTYPE html>" ;
"<html>" ;
"<body>" ;
"<embed src=\"" & $$PATH & "\"#toolbar=0&navpanes=0 width=\"865px\" height=\"7000px\"/>";
"<script type=\"text/javascript\">window.scrollTo(0," & $$NUMBER & ");</script>" ;
"</body" ;
"</html>"
)
KevinMortimer:
Webviewer behaviors depend on its browser engine and host OS.
So in some cases, they behave differently.
As far as I know,
--Windows: You can access local files from web viewer(data scheme)
not only ones in temporary path, but also in documents or in desktop
--Mac: You can only access files in temporary path from data scheme
--iOS: You can't access local files from data scheme, even in the temporary path.
Hi Sam
Thanks for the explanation. Currently i am able to view the pdf in my web viewer on my iPad when i export to the get ( temporaryPath ), but this only works if it is just the $$PATH set in the webviewer. As soon as i add the html code and javascript the webviewer is blank. So IOS is able to view local files in the Temp Folder unless i misunderstand what you mean by data schema
Hi KevinMortimer ,
I think that sam_oda has offered the correct explanation, but that there is a distinction that just needs to be teased out and highlighted in order for it to make sense.
The distinction is that, in the case where it works on iOS, the WebViewer is using a regular file URL. In the case where it does not work in iOS, the WebViewer is using a Data URL.
I think that what Sam is getting at is that:
Code which is loaded via a Data URL in the iOS is not allowed to reference the local file.
This is why he said "You can't access local files from data scheme, even in the temporary path.".
Alternatives that you might try out to see if they work:
1) Export your HTML code to the temporary path as well, and load the HTML using a file URL in the WebViewer (instead of a Data URL).
2) Include the actual PDF data in the HTML code by using a Data URL for the embed element's src attribute which passes along Base64 Encoded data.
I must mention, however, that I do not know how well embedding base64 data would work if the file size of the PDF file is very large. For smaller size files, I imagine it would work ok. Furthermore, I am not sure of which RFCNumber value you would want to supply to the Base64EncodeRFC function in FileMaker. (I'd probably start with 3548 and see what happens).
Hope this helps & sincerely,
-steve
ah....ok i am with you now. That now make sense. Thanks so much.
Update:
I figured out how to make the desired change in helpful status. Yay!
On a side note: I keep trying to mark sam_oda 's reply as helpful, but I notice that each time I do so and then reload the page, my designation shows up as "not helpful".
It's a shame, because, indeed, sam_oda 's reply is very helpful to this post.
Not sure if this is a large enough issue to warrant bringing to RosemaryTietge's attention.
I think that possibly I may have clicked the wrong button initially (though I am not certain about this), and if that's the case, I guess that the system is unable to allow one to amend such an error? Whatever the case, we can mentally add one to the helpful count on this one.
Sincerely,
-steve
Hi, Steve
Thank you for your thoughtfulness!
Hi KevinMortimer
The HTML references a path to the document that would be appropriate for Windows, but not iOS.
In order for it to work, you will need the HTML to vary slighyly by platform.
If you are not yet doing so, I would suggest taking care of that aspect, and see what happens.
Kind regards,
- steve