1 of 1 people found this helpful
WebKit 2.x doesn't really have much of printing support as far as I know.
yes, on Mac, but the same Mac with FM15 prints the web viewer content.
!I'm having the same issue here. When entering preview mode the web viewer becomes blank. If I use go to record / request [next] then go to record / request [previous] the web viewer will display it's content correctly but still be empty when saving as PDF. I'm only having this issue locally. If I'm running this on FMS 16 the web viewer content will show up in the PDF correctly.
I have the same issue.
Worked fine in FM 15 and now is Blank in FM 16.
I still didn't find the reason for this behavior. If there is for example my website shown in the web viewer the printing function works. So it is not because of that the webkit 2.0 doesn't support printing.
My workaround now is that I make a screenshot of the webviewer using the function in MBS. This screenshot is inserted into a container field. I now print a second layout showing the container instead of the webviewer - all only for Mac.
Once more a case where I need a completely different script and layout for each platform. I'm not very content with this additional effort. It is not getting better in FileMaker 16.
I employed the same workaround but it still falls short in that everyone who uses the solution needs the MBS plugin installed now, and the resolution from the MBS to container field is much worse than the web viewer so the result is pixelated images not high enough quality for printing (at least for us).
This is basic backwards compatibility and I really need this fixed in the next update.
So you need better screenshots?
Do you guys come to DevCon?
Maybe we can sit together and think about a few possible solutions.
just out of my mind, could it because the java code is not executed when previewing and printing ?
What happen if the contents of the WebViewer does include java scripts ?
Yes the screenshots could use better resolution. (or the option to set it)
Not at DevCon this year.
Ideally Filemaker will fix this issue and we won't need the container field workaround.
Better screenshots would be perfect. (I will not be at DevCon.)