Hello Diego,
We further investigated this ticket and this happens because the
"IWebBrowser2" interface, that we use to emulate HTML content, uses by default the Internet Explorer 7 engine for compatibility reasons. This is the default Microsoft implementation of the IE API that we use.
As a workaround, you can change the IE engine used by the "IWebBrowser2" interface by configuring the following registry key.
Code: Select all
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION
You should simply add under the
"FEATURE_BROWSER_EMULATION" key a DWORD registry value type set like this:
- Value Name: the name of your setup process (e.g. setup.exe)
Value Data: IE Version (e.g. 0x2AF9)
Also, please note that the IE version that you want to use by the IE emulation mode must be installed on your machine.
For instance, you can write your own
custom action which checks the higher IE version installed on current machine and set the "FEATURE_BROWSER_EMULATION" registry key accordingly. The custom action can be added as a custom action with sequence scheduled before "Wizard Dialogs Stage ->User Selection" action group.
If you have any questions just let us know.
All the best,
Daniel
FOLLOW US
Get the latest news in Application Packaging