The "IE browser" component is the most important one in your ebooks made with HTML Executable: it displays one or more HTML documents in the main window (subdivided if working with frames). These options are also related to the behavior of the WebBrowser control used to render HTML pages.
AllowIEGlobalOptions: indicates whether the menu command "Display Internet Explorer Options" is displayed or not. Note that the IE browser uses the same properties as Internet Explorer so if JavaScript is disabled for example in Internet Explorer, then it will be the same for your publication. This menu could let end users modify their Internet Explorer options, at least for the time they view your publication.
AllowModifyOpticalZoom: if enabled, menu commands named "Zoom In" and "Zoom Out" will be available in the "Navigate" menu, allowing users to increase or decrease the optical zoom.
AllowModifyTextSize: if enabled, a menu allowing users to increase or decrease the size of text used on Web pages is displayed.
AllowOtherCtxMenus: the main mouse context menu of Internet Explorer (the one which lets you show the source code of an HTML page) is automatically superseded by the publication's own context menu. However, some other context menus like for images are also available. If you want to disable these menus too, then set this property to False.
CustomUserAgent: lets you change the User Agent of the browser. If you leave it blank, the default user agent will be used (for instance, with IE9 installed, it could be "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)").
It is possible to keep the original user agent thanks to the %ORIGINAL% variable. For instance, enter this in CustomUserAgent property: "%ORIGINAL% my string" (without quotes) and the user agent will be something like: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E) my string
DonotProcessEnterKeyMsg: (false by default). Turn this property to True if you get troubles with the ENTER key in HTML editors such as FCKEditor.
EnableIE9GPUMode: allows your publication to use GPU Rendering mode (hardware acceleration). By default, it will use Software Rendering mode. Only applicable if Internet Explorer 9 is installed on the end user's computer.
IEStatusBar: if enabled, the status bar (see above) will work like the Internet Explorer one. It can then be accessed via JavaScript commands too.
No3DBorder: if true, removes the 3d border of the IE browser.
NoAutomaticPopup: if true, IE publications won't display any popup window automatically. Internal link targets are ignored and links to websites with the _blank target are displayed in the default web browser; it mimics the behavior of publications made with HTML Executable 3.2.
NoForceIEStandardMode: when set to False (default), webpages are displayed in IEn Standards mode, regardless of the !DOCTYPE directive. When set to True, only webpages containing standards-based !DOCTYPE directives are displayed in IEn mode. (n = 8 if IE8 is installed, n = 9 if IE9 is installed).
NoMultiThreading: when set to True, it disables multi-threading support in IE publications. Turn this property to True if you get troubles with your publication (application crashes or freezing, for instance when running some Flash movies in Windows XP).
NoScrollbar: if true, removes the scrollbars of the IE browser. Not recommended.
ScriptNoErrorMsg: if true, this disables the automatic Script Error dialog box when a JavaScript/VBScript error is found in an HTML page by the Internet Explorer engine.
SearchFrameTarget: important property if you use frames in your publication and if the search engine is active. When a search is complete, it displays links to the found HTML documents so end users can open them. You can specify in which frame these documents should be opened, otherwise if you leave this property blank, the frame system will be ignored. Note that this is only supported by IE publications.
SearchResultShowSpanStyle: when a search through a publication is done, end users can click on a search result and the associated page is displayed. Then the publication will automatically try to highlight the words of the search query. Highlighting is actually done by changing the text style of the word(s): you can define the HTML style attribute you want (CSS syntax). By default it is: background-color: Lime; font-weight: bolder;
UseIE7CompatibilityMode: if true, your publication will use the IE7 rendering engine, even if IE8 or IE9 is set up. Only useful for compatibility purposes.