This document describes known bugs that you may see in this release of HotJava for Solaris. These bugs are divided into the following categories:

• General Browser Functions
• HTML Support and Page Display
• Miscellaneous

General Browser Functions

• If your site requires a user id and password to connect outside of your firewall, you will be prompted by HotJava Browser for your id and password every time you access an external Web page, instead of only once per session. (4067992)

• A JDK^TM software bug prevents the HotJava Browser from parsing URLs in the format protocol://user:passwd@host:port correctly. Instead, it assumes a host:port format when it encounters the colon (:) separating user and passwd . This will be fixed when HotJava Browser ships with JDK 1.2. (4086109 and 4087121)

• HotJava Browser can hang if you attempt to launch multiple modal dialogs in quick succession. (4088423)

• The Stop button is disabled when the primary document's text has finished loading, even if the document contains images or other elements that are still loading. (4033287)

• The Edit->Find in Document feature does not work when viewing a page with frames. (4086675)

• On the Edit->Preferences pages, the Reset buttons do not always work. (4111955)

• Due to the HotJava Browser's security manager, some Swing applets will not work in HotJava. Swing applets may also cause the browser to hang. (4125348, 4123604)

• File downloads fail silently if you do not have write permission to the directory where you're trying to save the file. (4120256)

• An SSL certificate error prevents an HTTPS page from loading if the server name on the site certificate does not exactly match the server host name. This may happen, for example, if the "www" portion of a host name is missing or replaced with an asterisk (*) on the site certificate. In such a case, you are presented with a dialog asking if you want to trust the certificate for this session or always, but even if you choose to trust the site, the connection fails. (4101303)

• When loading a page with a signed applet, sometimes the applet's certificate does not show up on the Advanced Security Settings page, making it impossible to set permissions. If this happens, a workaround is to quit the HotJava Browser and restart it. The certificate should appear after the browser is restarted. (4145426)

• The HotJava Browser User's Guide should note that the HotJava Browser should not be running when you edit your personal properties file. Otherwise, your edits will be lost when you quit the current browser session. (4129549)

HTML Support and Page Display

• Web pages with "Refresh" attributes do not get refreshed if you navigate away from them and then return. A workaround is to reload the page upon revisiting it. (4093330)

• HotJava Browser does not distinguish upper- and lower-case letters in the target URL for a "Refresh" attribute. All letters in the URL are converted to lower-case. (4121954)

• If an HTML form does not contain an "action" parameter, the form submit will fail. (4133890)

• If the ROWS attribute of <FRAMESET> tag contains an "*" (asterisk), frames of equal width are created. The row height values are not honored in this case. (4108035)

• If attributes such as BORDER, FRAMEBORDER, and FRAMESPACING are set to 0 within a <FRAMESET> tag, the border is still displayed as a thin, gray line. (4060479)

• HotJava Browser should prevent text and punctuation from being separated by a line break.

  For example, if an HTML tag or entity occurs just before the period at the end of a sentence, the period is not guaranteed to stay with the last word of the sentence and may appear by itself on the following line. One possible workaround for Web page developers is to surround the text and punctuation that should stay together by <NOBR><WBR> and </NOBR>. (4041336)

• Extremely large documents do not display completely in the HotJava Browser. (4005977)

Cookie Problems

• Some sites report a generalized "cookie error" when attempting to connect with HotJava Browser. We are looking into this problem to determine the cause. (4128730)

• Non-persistent cookies are stored in HotJava Browser's cookies file, and they should not be. (4125409)

• Cookies are not returned to the server on fetches of most objects other than HTML pages, such as .class files, .jar files, and images. (4119950)

• Cookies are not sent or stored when applets make URL connections. (4144090)

• Cookies stored in the HotJava Browser cookies file do not have the port number stored with the domain, which is required when the Web server is not on the default port 80. (4125057)