If you control the source to the content you want to display, you can include this in the section of the HTML document:Īnd also use HTML5 DOCTYPE at the start of the document: Name) = CType( 11000, Int32)Īnother to to keep in mind is if Internet Explorer 11 has the option "Display intranet sites in Compatibility View" selected in the "Compatibility View Settings" pane, then IE will most likely still render using IE7. Var reg As New RegistryItem( "HKEY_CURRENT_USER\SOFTWARE\Microsoft")
#Xojo html viewer code
This code handles both 64 and 32-bit builds This is how you can change it using Xojo: You can tell Windows to use a newer version of the IE rendering engine with a Registry setting. This may result in web pages that do not display or work as you expect. On Windows, the Native Renderer is probably using an older version of the Internet Explorer renderer. When using WebKit on Windows, HTMLViewer.Handle returns a pointer to the cef_browser_t struct. To make plugins available to WebKit on Windows, create a folder called WebKitPlugins within your Libs folder in your application folder and place the plugins you need there. Using WebKit on Windows adds the entire Chromium Embedded Framework 3 (CEF3) engine to your app, increasing its size by about 100MB. You can use WebKit on Windows by setting the Renderer property to WebKit (1). You can work around this by providing a plist with your app to indicate what non-secure URLs you are using.
Starting with MacOS 10.11 and Xojo 2018r4, your apps have to use secure "https" connections or you will get this error: "The resource could not be loaded because the App Transport Security policy requires the use of a secure connection". On macOS, the HTMLViewer supports getting and setting a custom user agent string and increasing or decreasing the font size.
Renders HTML and provides basic navigation features.