The following list shows known limitations that occur when end users view a WebHelp project using a specific browser. This information is only for reference and may not apply to every WebHelp project.
Due to security issues, references to HTML pages located at the root of any drive (or a network drive mapped to a letter drive so it appears to be a root drive) will not work properly. This includes references in the table of contents, the index, and within topics.
Contents and Index do not display from the root drive or a network drive mapped to a letter drive (so it appears to be a root drive).
Cascading style sheets are not supported. Only embedded and inline styles display.
Dynamic HTML is not supported. All Dynamic HTML effects display as static effects.
Java applets do not resize when browser is resized.
The FONT FACE tag is not supported. Text uses the default font of the browser.
Microsoft has documented that HTML files do not always display if users request the files in rapid succession. Users can return to a previously displayed page and then reselect the page that didn't display.
In Internet Explorer 3.00 and 3.01 Java applets cannot read or write local or network media. Therefore, WebHelp can only be accessed via a Web server.
Navigator cannot load Java applets from locations specified by uniform naming convention file names (e.g., \\server\share\start.htm) on local area networks. This problem can be solved by mapping a drive letter to the share.
ActiveX technology is not directly supported.
Dynamic HTML is not supported. All Dynamic HTML effects display as static effects.
Cascading style sheets are not supported. Only embedded and inline styles display.
Margin settings are ignored. This results in a small, unused margin area surrounding the WebHelp navigation pane.
Java applets do not resize when browser is resized. (This was fixed in version 4.61.)
Hyperlinks in a popup window display the target in the popup window and not in the main content frame.