General XMetaL Discussion
paorear December 17, 2014 at 2:32 am
XMetaL 8.0 Enterprise: Internal browser/preview issueDecember 17, 2014 at 2:32 amParticipants 2Replies 3Last Activity 7 years, 9 months ago
Hi guys – we do some significant tweaking of the processing logic to create an HTML page for preview. When we load it in response to the preview event, it loads successfully, but it doesn't seem to render as we desire.
Are you using the Windows Shell IE web browser component, or some other browser component?
If we instead use Preview in browser and point to iexplore.exe, all displays as expected.
Why would the external browser preview correctly, but not the internal?
Any help greatly appreciated!
Paul O'RearXMetaLOldTimer December 17, 2014 at 9:21 pm
Reply to: XMetaL 8.0 Enterprise: Internal browser/preview issueDecember 17, 2014 at 9:21 pm
Yes, XMetaL's Page Preview is implemented by hosting the Shell IE web browser control. XMetaL will call the control's Navigate2() API passing the BrowserURL property value that your custom script setup.
I am not sure about robustness of said script running within just the IE control versus the stand-alone IE application…but, it is unlikely that is causing your issue. I suspect Windows Firewall or similar is blocking the XMetaL process from fetching content over http/https.
Addampaorear December 17, 2014 at 9:24 pm
Reply to: XMetaL 8.0 Enterprise: Internal browser/preview issueDecember 17, 2014 at 9:24 pm
Thanks Addam – I was suspecting that with the firewall, too, but have not been able to isolate anything like that yet.
Paul O'Rearpaorear December 18, 2014 at 8:16 pm
Reply to: XMetaL 8.0 Enterprise: Internal browser/preview issueDecember 18, 2014 at 8:16 pm
I found the solution to the issue via this blog post:
and this documentation:
Apparently, the web browser control when hosted in an application defaults to the IE 7 rendering mode. There's no easy way to say “use the latest version” when hosting the control. You can, however, specify a simple registry entry on a per .exe basis that then effectively enables the desired emulation mode for the host application.
The problem in my case was that we were leveraging some HTML 5 CSS features that were not supported in IE 7. Making this tweak solved everything.
Hopefully this may help others as well.
- You must be logged in to reply to this topic.