In Merlin Beta 3, the "Serialized Form" links in the class documentation pages no longer reference anchors to bring the browser to the appropriate class within the larger serialized form page. This is generally inconvenient, and particularly inconvenient with the J2SE serialized form page because it is so massive that it is quite cumbersome to find the desired class manually.
In previous versions (including Merlin Beta 2), the "Serialized Form" links would take the browser to the appropriate anchor within the larger serialized form page for the current class.
As an example, consider the J2SE documentation itself-- compare equivalent cases from the following public documentation sets:
Choose the class java.rmi.MarshalledObject and click on the "Serialized Form" link from each one. In the 1.3 documentation set, the current frame goes to the combined serialized form page correctly positioned at the serialized form for the MarshalledObject class, presumably because the "Serialized Form" link references the appropriate anchor; from the HTML source of the 1.3 page:
<A HREF="../../serialized-form.html#java.rmi.MarshalledObject">Serialized Form</A>
In the 1.4 documentation set, the combined serialized form page is brought up in a new window with the browser at the top of the document; compare the HTML source of the 1.4 page:
<A HREF="../../serialized-form.html" TARGET="java.rmi.MarshalledObject">Serialized Form</A>
The anchor is gone from the relative URL of the HREF attribute, and there is a TARGET attribute identifying the desired class instead. I don't think that this is a correct used of the TARGET attribute (at least it doesn't seem to have the desired effect on Netscape 4.76 and IE 4.x), and I think that it's also what's created the serialized form page to be brought up in a new window.