Name: rmT116609 Date: 04/29/2003


FULL PRODUCT VERSION :
java version "1.4.2-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-beta-b19)
Java HotSpot(TM) Client VM (build 1.4.2-beta-b19, mixed mode)

FULL OS VERSION :
Microsoft Windows 2000 [Version 5.00.2195]

I'm running w/SP3 (Service Pack 3)

EXTRA RELEVANT SYSTEM CONFIGURATION :
I'm using Internet Explorer 6.0.2800.1106.

I used the "most open" security settings possible in IE.

Specifically, I made sure the "Navigate sub-frames across different domains" was enabled for all my zones. I tried to eliminate IE security as a cause for this problem.

A DESCRIPTION OF THE PROBLEM :

I realize Bug #4645058 is declared "fixed" but it seems not to be. I still get the same JavaScript error when using IE 6. I have not tried other browsers.

First, using IE 6, go under "Tools | Internet Options...", select the "Advanced" tab and make sure the option, "Display a notification about every script error" is checked. This will ensure a dialog window appears for each JavaScript error.

Next, I run the javadoc tool with the "-link" option. Then, I browse the generated docs. Everythink looks good -- I see the documentation for my classes as well as the JDK classes (e.g., java.lang.* classes, etc.). When I browse the javadocs for one of these JDK classes, however, I see the JavaScript error described in 4645058:

The JavaScript Error I see is a dialog window:
........
Line: 17
Char: 5
Error: Access is denied
Code: 0
........

As you'll see from looking at the JavaScript, the problem has to do with trying to set the parent document's title to reflect the class being browsed.

Note that the line/column numbers where my error occurs are different from those reported in Bug 4645058 since I'm using JDK v1.4.2 and Bug 4645058 was filed against v1.4.0.

Also, note that the HTML generated by javadoc does indeed have
the "<SCRIPT type="text/javascript">" line as indicated in the Bug Fix 4645058. The javadoc for the external JDK classes also has this line so I'm sure everything is linked up correctly. Even so, the JavaScript error still appears.



STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
See "Description" section above.


ERROR MESSAGES/STACK TRACES THAT OCCUR :
See "Description" section above.

REPRODUCIBILITY :
This bug can be reproduced always.
(Review ID: 184911)
======================================================================