Netscape Developer Release Notes

These developer release notes, last updated 9 May, 2003 11:32 PM PST, describe known issues for developers in Netscape. This document may be updated from time to time. To learn more about developing and maintaining content, see Netscape DevEdge Online, which helps developers learn about the tools and information they need to create compatible web sites and applications that operate in a cross browser world.

These release notes document known bugs in Netscape with web standards compliance and support for Java, JavaScript, and Plug-ins that developers have asked be documented in the product release notes. (This is not a complete list of every single reported bug; for that, see the Bugzilla bug database, which tracks open bugs in the Mozilla browser upon which Netscape is based.) To learn more about Netscape Gecko, read the Gecko FAQ on mozilla.org and visit the Gecko Developer Area on DevEdge Online. If you're interested in the general topic of evaluating standards compliance, you may want to read this essay on the topic.

Mozilla, Netscape , and the browser engine they share are continually being improved. You can contribute to standards compliance in browsers:

Start by checking the mozilla.org Get Involved page.
If you're a C++ engineer, find a helpwanted bug in Bugzilla.
If you're a web content or web application developer or someone who knows HTML, CSS, JavaScript, and/or the W3C DOM:

Make sure your web site is standards-compliant and that it will work as well on standards-compliant browsers as on other browsers.
Join the BugAThon to help analyze and simplify down to test cases bugs that have been reported already.
Volunteer on netscape.public.mozilla.documentation to join the Mozilla Open Source Documentation Project and help document standards compliance in browsers for reference by developers everywhere.

Download the latest Mozilla milestone build from mozilla.org, or better yet a recent daily build, surf with it, and report any bugs or crashes you discover so that the open-source Mozilla codebase, on which all releases of Netscape 6 will be based, keeps improving.

HTML

Bug # (if any)	Issue
For more information, see these Bugzilla entries: 36045 31932 ... and this note by David Baron	The following behavior is not a bug, but a feature that developers should be aware of. Mozilla has two layout modes: quirks mode ("backward compatibility mode") and standard mode. The quirks mode mimics the behavior of Netscape Navigator 4.x to provide backward compatibility with legacy content on the web, while the standards mode aims to comply strictly with the Recommendations of the World Wide Web Consortium. The mode is picked based on the doctype declaration (or the lack thereof) at the beginning of an HTML document. Here are simple guidelines for picking a doctype declaration to ensure your documents display as desired both in Netscape 6 and in older browsers: A) For legacy HTML documents that have not been checked for HTML 4.0 compliance and which may rely on the behavior of old browsers (i.e. most documents on the web today): no doctype declaration, or any doctype declaration other than those listed in (B) or (C) B) For documents that you want to be laid out strictly according the to the standards on Mozilla, Netscape 6, and other Mozilla-based browsers and appliances, but in which you wish to include presentational hints using deprecated tags of HTML to ensure acceptable formatting on older browsers (i.e. documents that comply with the CSS2 box layout model* and validate as HTML 4.01 Transitional, so they may contain deprecated markup for legacy browsers), use the HTML 4.01 Transitional doctype declaration with the URI, i.e.: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> C) For documents that you want to be laid out strictly according the to the standards on Mozilla, Netscape 6, and other Mozilla-based browsers and appliances, and from which you have eliminated deprecated tags of HTML (i.e. documents that comply with the CSS2 box layout model* and validate as HTML 4.01 Strict), use the HTML 4.01 Strict doctype declaration, i.e.: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> * Please note that in the CSS2 box layout model the default vertical sizing of layout boxes and the default vertical alignment of images is different from the behavior of old browsers and the quirks mode. http://www.w3.org/TR/REC-CSS2/visudet.html#q15 http://www.w3.org/TR/REC-CSS2/visudet.html#propdef-vertical-align These aspects of the layout can be changed by explicitly overriding the defaultvalues via a CSS style sheet.
	BASEFONT is deprecated and will not be supported in Netscape 6.
	BDO is not implemented.
	The following HTML attributes are not supported: shape attribute on the A element, abbr, axis, headers, scope-row, scope-col, scope-rowgroup, scope-colgroup, charoff, datasrc, datafld, dataformat, datapagesize, summary, event, dir, align on table columns, label attribute of OPTION, alternate text of AREA elements, longdesc
	Various metadata attributes are not supported: cite, datetime, lang, hreflang.
55285	Mozilla currently assumes that all white-space within a <button> element is significant. This can be changed as required by using stylesheets. For example, to allow the text in a button to wrap, you would use this: button { white-space: normal; } Note that doing this with small labels may make buttons appear too small, in which case judicious use of the 'padding' and 'width' properties may be of use.
14445	<input type="radio"> is not mutually exclusive without an enclosing form element. The workaround is to enclose the INPUT elements within a containing FORM element.
26644	HR width percentage value not working in button element.
33654	Form input elements and textareas will not use the font face specified by <FONT> tags that enclose them. As a workaround, the author of the web page can use style to explicitly set the font used by input elements or textareas, or they can add the following style to the <HEAD> portion of their document so that input elements and textares use the face specified by the <FONT> tag: font input { font: inherit; } font textarea { font: inherit; } TEXTAREA incorrectly applying ROWS= and COLS=
34297	Form controls with style="display: none;" are not submitted.
36003	If a table is inside a fieldset and has align=left or align=right, the table is rendered outside the fieldset, and only partially. Setting align=none or removing the align attribute eliminates the problem.
40545	LABELs on OPTIONs (<option label> in selects) are silently ignored.
40680	The 'codebase' attribute of the OBJECT element doesn't affect relative URIs in the 'data' attribute value. Workaround: use absolute URIs in the OBJECT's 'data' attribute value when 'codebase' attribute is present.
44065	The HTML 4.01 specification states that for <input type="file" ...>, the SIZE attribute should be interpreted as a value in pixels, but Netscape 6 currently interprets this as a number of characters.
59037	The "rules" attribute of the HTML 4.01 TABLE element is ignored. Workaround: use the CSS "border" property for individual table rows or table cells if rule attribute values other than "none" or "all" are needed.
55686	Earlier versions of Netscape browsers allowed the user to Alt+Click on a link (on the Windows and Unix platforms) or Option+Click (on the Macintosh platform) to save the file pointed at by the link on the local drive. Netscape 6 does not support this feature in the first release.
52019	The HTML 4.01 specification states that the SIZE attribute of the FONT element should contain only integers. Using non-integer values may result in unwanted behaviour. Specifically, a decimal number starting with dot "." will be interpreted as if there was no dot, so ".5" will be interpreted as "5".
52746	Dynamic fonts are not supported. Browser sniffing can be used to detect Netscape 6 and serve different content.
44464	The HTML 4.01 specification states that <input type="file" ...> should be able to select one or more files for upload, but Netscape 6 only allows one file to be selected for upload. Workaround is to use multiple file inputs, as with many other existing web browsers.

For a list of current open HTML bugs on the Mozilla browser (upon which Netscape 6 is based), see:

Elements, Form Controls, Frames, Tables, and Form Submission
bug reports marked with the html4 keyword
"meta bug" for tracking outstanding issues with HTML 4.01 compliance

If you are an HTML developer who has questions about using HTML in Mozilla and Netscape 6, post your questions in the netscape.public.dev.html newsgroup.

XML

Bug # (if any) Issue

Processing to manipulate default attributes is not implemented.

57164 Mozilla currently does not support the 'charset' pseudo-attribute of the XML Stylesheet Linking PI. Workaround: Use the CSS2 @charset rule to specify the encoding as the first rule in your stylesheet.

For a list of current open XML bugs on the Mozilla browser (upon which Netscape 6 is based), see the XML component. If you are an XML developer who has questions about using XML in Mozilla and Netscape 6, see the XML Area on DevEdge and post your questions in the newsgroup.

For a list of current open XHTML bugs on the Mozilla browser (upon which Netscape 6 is based), see bugs marked with the xhtml keyword.

CSS1

If you are a CSS developer who has questions about using CSS in Mozilla and Netscape 6, see the CSS Area on DevEdge and post your questions in the netscape.public.dev.css newsgroup.

Bug # (if any) Issue

Styles cannot be applied to HTML columns.

32372 Author styles cannot be turned off.

The

20582 The current release of Mozilla does not correctly support the <hr> element in combination with CSS. In particular, when the body uses padding, <hr> elements are prone to being drawn in the wrong place. Work around: Instead of using the <hr> element, use semantic markup and then place borders on that. For example, instead of:
      <h1> Welcome </h1>
      <p> Welcome to my page. </p>
      <hr>
      <h2> Status </h2>
      <p> All is well. </p>
...use
      <h1> Welcome </h1>
      <p> Welcome to my page. </p>
      <h2> Status </h2>
      <p> All is well. </p>
...with a stylesheet containing:
      h2 { border-top: thin groove; padding-top: 1em; margin-top: 0; }
...adjusting the style as required to get the wanted effect.

5693 :hover works for an individual element such as A and its contents, but if used for a block-level element such as a DIV, the :hover behavior does not inherit to enclosed children of the block-level element.

53985 Mozilla currently does not ignore whitespace before a <br>, which in certain rare cases can cause an extra blank line to be inserted in the rendering. See bug 53985 for more details. Workaround: remove any spaces before a <br> element, or avoid use of this element altogether.

30802 Percentage left padding fails on one-line blocks.

1777 'text-decoration' of parent elements (such as underline) are currently drawn across child elements.

17644 If a P starts with an image followed by text,, has a negative text-indent, and the negative text-indent is the same width as the image, the text overwrites the image. The workaround is to change the size of the image (perhaps by adding additional transparent pixels) or the size of the text-indent so that they are not identical.

19963 dotted and dashed borders don't interact well with other types of borders.

20163 'text-decoration' (such as underlines) affects the formatting of text-less inlines, although it should not.

20582 HR rules are not obeying the CSS padding of the BODY.

Known issues with float:

41412 Text may overlap the top edge of a float that is pushed down on the page.

13610 :first-letter does not inherit from :first-line when floated.

For a list of current open CSS1 bugs on the Mozilla browser (upon which Netscape 6 is based), see the Style System component and bug reports marked with the css1 keyword.

CSS2

Bug # (if any) Issue

53663 The value 'auto' on the 'top' and 'left' properties on tables is not supported. It is treated as '0' instead. As a work around, authors can wrap positioned <table> elements in a <div>, and position that, instead. For example, instead of:
      <table style="position:absolute"> ...   </table>
...authors could use:
      <div style="position:absolute"><table> ...   </table></div>
This should have a similar effect.

2055 Compact DL is not supported.

9109 The CSS visibility property has no effect on frames.

51678 Using incorrect values for the 'rect()' value of the 'clip' property can cause unexpected results. Workaround: do not use incorrect values for that property!

46891 Generated content of attr(xxx) on an <A> is not clickable (does not load new url)
There is a workaround for some usages. Instead of this:
   a:before { content: attr(title); }
   ...
   <a href="test.html" title="Hello World"></a>
Try this :
   a:before { content: 'Hello World'; }
   ...
   <a href="test.html"></a>

For a list of current open CSS2 bugs on the Mozilla browser (upon which Netscape 6 is based), see the Style System component and bug reports marked with the css2 keyword.

CSS3

Bug # (if any) Issue

53796 When used in conjunction with the proposed CSS3 namespace selectors, simple selectors that do not include a universal selector or a type selector will be erroneously assumed to match elements in namespaces, instead of only the default namespace. Workaround: explicitly give the universal selector in those cases as recommended by the CSS Specification. For example, instead of:
      @namespace url(http://www.w3.org/1999/xhtml);
      :link, :visited { text-decoration: underline; }
...which would also match X-Links, you should use:
      @namespace url(http://www.w3.org/1999/xhtml);
      *:link, *:visited { text-decoration: underline; }
...which will correctly match only HTML links (<a>, <area>, and <link>).

For a list of current open CSS3 bugs on the Mozilla browser (upon which Netscape 6 is based), see the Style System component and bug reports marked with the css3 keyword.

CSS Extensions in Mozilla

Bug # (if any) Issue

The names of certain Mozilla extension pseudo-classes lack the moz- prefix.

The experimental -moz-opacity property has known crash bugs, is not supported, and may be renamed in a future release.

For a list of current open CSS extension bugs on the Mozilla browser (upon which Netscape 6 is based), see the Style System component and bug reports marked with the css-moz keyword.

DOM0

If you are a DOM developer who has questions about using the W3C DOM in Mozilla and Netscape 6, see the W3C DOM Area on DevEdge and post your questions in the netscape.public.dev.dom newsgroup.

Bug # (if any) Issue

22681 The contents of a dynamically-created IFRAME cannot be modified using the IFRAME's window.document.write() method because the window.document object is null.

33728 setTimeout on Function.prototype.apply causes a crash.

53350 Parent window forces itself above child popup windows. If a page uses window.open() to open popup windows in an inline script, the parent window will place itself on top of the popup windows once the parent has finished loading. The workaround is to place the window.open() in the parent's "load" event handler.

For a list of current open DOM0 bugs on the Mozilla browser (upon which Netscape 6 is based), see the DOM0 component.

W3C DOM1

Bug # (if any) Issue

88318
Dynamic script evaluation now works (new SCRIPT elements attached to a document via the DOM result in script evaluation. The caveat to this improvement is that subsequent modification of a SCRIPT element does not retrigger evaluation.

For a list of current open DOM1 bugs on the Mozilla browser (upon which Netscape 6 is based), see the DOM1 component.

W3C DOM2

Bug # (if any) Issue

1572 Key events are not cancellable. Returning false still allows character entry into edit fields.

13213 Events don't reach elements to the top or left of view.

53118 Certain events bubble that should not bubble. These are: "load" (except when caused by image load), "unload", "focus" and "blur". Specifically note that this affects the HTML attributes "onload", "onunload", "onfocus" and "onblur" as well. The workaround is to explicitly stop the bubbling of these events by calling the stopPropagation() method of the event or use browser sniffing and execute a different code path for Netscape 6. Scripts should not depend on this feature as it will be fixed in a future release.

For a list of current open DOM2 bugs on the Mozilla browser (upon which Netscape 6 is based), see the DOM2 and Event Handling components.

RDF

Bug # (if any) Issue

aboutEach, aboutEachPrefix, and parseType aren't supported.

For a list of current open RDF bugs of the Mozilla browser (upon which Netscape 6 is based), see the RDF component. If you are an RDF developer who has questions about using RDF in Mozilla and Netscape 6, see the RDF Area on DevEdge and post your questions in the netscape.public.dev.rdf newsgroup.

JavaScript

If you are a JavaScript developer who has questions about using in Mozilla and Netscape 6, see the JavaScript Area on DevEdge and post your questions in the netscape.devs-javascript newsgroup. (If you have questions about using the W3C DOM in Mozilla and Netscape 6 from JavaScript, see the W3C DOM Area on DevEdge and post your questions in the netscape.public.dev.dom newsgroup.)

Bug # (if any) Issue

Date.toDateString and Date.toTimeString are not implemented.

37333 Some features of signed scripts in Navigator 4.x are not yet implemented in Mozilla or Netscape 6, including <SCRIPT ARCHIVE=> and ID= tags.

For a list of current open JavaScript bugs on the Mozilla browser (upon which Netscape 6 is based), see the JavaScript engine component.

Plug-ins

For information about the enhanced Mozilla Plug-in API supported in Mozilla and browsers based upon it such as Netscape 6, see the Mozilla Plug-in API documentation on the mozilla.org web site.

Bug # (if any) Issue

The following three points are not bugs, but are noted here as an FYI for users and developers:

1) On Mac OS only, the name of the folder for installing plug-ins is "plug-ins" with a hyphen (for backward compatibility with Communicator 4.x for the Mac and legacy plug-in installer binaries), not "plugins" as on Windows and Linux.

2) On Windows only, if RealPlayer, Flash, or Acrobat are installed in the Communicator 4.x plugins directory but are not installed in the Netscape 6 plugins directory, Netscape 6 will load these plugins from the Communicator 4.x plugins directory. For other plug-ins, and on other platforms, either:

rerun the installer for the plug-in, instructing it to install into the Netscape 6 plugins directory (which is named "plug-ins" on Mac only), or

copy the files for that plug-in over from the Communicator 4.x plugins directory into the Netscape 6 plugins directory (which are both named "plug-ins" on Mac only)

3) If a legacy Communicator 4.x plug-in binary is installed within Mozilla or Netscape 6, its basic features will function as expected because of the backward compatibility of the Mozilla Plug-in API supported by Netscape 6. However, if the plug-in has a Java API callable from JavaScript via LiveConnect, these calls within will fail silently until the plug-in binary is upgraded to support the Mozilla Plug-in API. Contact the plug-in vendor to determine when an upgraded plug-in binary will be available for download.

(Mac OS) QuickTime movies are not displayed correctly, and are offset on the page.

(Mac OS) If you are watching a Flash or QuickTime movie and you open the Preferences dialog or perform other tasks in which dialog boxes appear, the dialog boxes appear blank. To correct this problem, close the page you are viewing and then perform your task.

For a list of current open plug-in bugs on the Mozilla browser (upon which Netscape 6 is based), see the Plug-ins component.

Java

Bug # (if any) Issue

Netscape 6 includes Java 2 Standard Edition (J2SE) Runtime Environment v1.3.1_01. This release of J2SE was created specifically for support of Netscape 6. Installing Netscape 6 will not disrupt other Java Runtime Environments you may have installed (for instance, JRE 1.3.1, 1.3, or JRE 1.3.0_01 downloaded from java.sun.com). This is the same release that's available from Sun.

Netscape 6 has been tested only with J2SE v1.3.0_01. Other J2SE releases, or previous JDK's from Sun, will not work with Netscape 6.

(Mac OS only) You must have Mac OS Runtime for Java (MRJ) version 2.2 to run Java aplets with Netscape 6. If you have Mac OS version 8.5 through 8.6, you may need to upgrade your version of MRJ. For an upgrade, go to the Apple software download pages.

Running J2SE in Netscape 6 in 256 color mode may cause a flicking problem.

(Linux) Netscape 6 on Linux and Solaris includes includes J2SE v1.3.0_01. The Java support on Linux and Solaris is not complete (for instance, LiveConnect is not yet enabled), but will be functional in a later release.

For a list of current open bugs on the Mozilla browser (upon which Netscape 6 is based), see the OJI component.

If you are a Java developer who has questions about using Java in Mozilla and Netscape 6, see the java.sun.com web site.

Other

Bug # (if any) Issue

46318 XP Install: Malformed XPI javascript install triggers may cause the installation to hang until the browser's "Stop" button is pressed (or prevent installation entirely on Linux). The correct syntax, which does not cause a hang, is:
InstallTrigger.install( {"pretty name": "url"} );

Last updated 9 May, 2003 11:32 PM PST

Bug # (if any)	Issue
	Processing to manipulate default attributes is not implemented.
57164	Mozilla currently does not support the 'charset' pseudo-attribute of the XML Stylesheet Linking PI. Workaround: Use the CSS2 @charset rule to specify the encoding as the first rule in your stylesheet.

Bug # (if any)	Issue
	Styles cannot be applied to HTML columns.
32372	Author styles cannot be turned off.
	The
20582	The current release of Mozilla does not correctly support the <hr> element in combination with CSS. In particular, when the body uses padding, <hr> elements are prone to being drawn in the wrong place. Work around: Instead of using the <hr> element, use semantic markup and then place borders on that. For example, instead of: <h1> Welcome </h1> <p> Welcome to my page. </p> <hr> <h2> Status </h2> <p> All is well. </p> ...use <h1> Welcome </h1> <p> Welcome to my page. </p> <h2> Status </h2> <p> All is well. </p> ...with a stylesheet containing: h2 { border-top: thin groove; padding-top: 1em; margin-top: 0; } ...adjusting the style as required to get the wanted effect.
5693	:hover works for an individual element such as A and its contents, but if used for a block-level element such as a DIV, the :hover behavior does not inherit to enclosed children of the block-level element.
53985	Mozilla currently does not ignore whitespace before a <br>, which in certain rare cases can cause an extra blank line to be inserted in the rendering. See bug 53985 for more details. Workaround: remove any spaces before a <br> element, or avoid use of this element altogether.
30802	Percentage left padding fails on one-line blocks.
1777	'text-decoration' of parent elements (such as underline) are currently drawn across child elements.
17644	If a P starts with an image followed by text,, has a negative text-indent, and the negative text-indent is the same width as the image, the text overwrites the image. The workaround is to change the size of the image (perhaps by adding additional transparent pixels) or the size of the text-indent so that they are not identical.
19963	dotted and dashed borders don't interact well with other types of borders.
20163	'text-decoration' (such as underlines) affects the formatting of text-less inlines, although it should not.
20582	HR rules are not obeying the CSS padding of the BODY.

	Known issues with float:
41412	Text may overlap the top edge of a float that is pushed down on the page.

13610	:first-letter does not inherit from :first-line when floated.

Bug # (if any)	Issue
53663	The value 'auto' on the 'top' and 'left' properties on tables is not supported. It is treated as '0' instead. As a work around, authors can wrap positioned <table> elements in a <div>, and position that, instead. For example, instead of: <table style="position:absolute"> ... </table> ...authors could use: <div style="position:absolute"><table> ... </table></div> This should have a similar effect.
2055	Compact DL is not supported.
9109	The CSS visibility property has no effect on frames.
51678	Using incorrect values for the 'rect()' value of the 'clip' property can cause unexpected results. Workaround: do not use incorrect values for that property!
46891	Generated content of attr(xxx) on an <A> is not clickable (does not load new url) There is a workaround for some usages. Instead of this: a:before { content: attr(title); } ... <a href="test.html" title="Hello World"></a> Try this : a:before { content: 'Hello World'; } ... <a href="test.html"></a>

Bug # (if any)	Issue
	The names of certain Mozilla extension pseudo-classes lack the moz- prefix.
	The experimental -moz-opacity property has known crash bugs, is not supported, and may be renamed in a future release.

Bug # (if any)	Issue
22681	The contents of a dynamically-created IFRAME cannot be modified using the IFRAME's window.document.write() method because the window.document object is null.
33728	setTimeout on Function.prototype.apply causes a crash.
53350	Parent window forces itself above child popup windows. If a page uses window.open() to open popup windows in an inline script, the parent window will place itself on top of the popup windows once the parent has finished loading. The workaround is to place the window.open() in the parent's "load" event handler.

Bug # (if any)	Issue
88318	Dynamic script evaluation now works (new SCRIPT elements attached to a document via the DOM result in script evaluation. The caveat to this improvement is that subsequent modification of a SCRIPT element does not retrigger evaluation.

Bug # (if any)	Issue
1572	Key events are not cancellable. Returning false still allows character entry into edit fields.
13213	Events don't reach elements to the top or left of view.
53118	Certain events bubble that should not bubble. These are: "load" (except when caused by image load), "unload", "focus" and "blur". Specifically note that this affects the HTML attributes "onload", "onunload", "onfocus" and "onblur" as well. The workaround is to explicitly stop the bubbling of these events by calling the stopPropagation() method of the event or use browser sniffing and execute a different code path for Netscape 6. Scripts should not depend on this feature as it will be fixed in a future release.

Bug # (if any)	Issue
	aboutEach, aboutEachPrefix, and parseType aren't supported.

Bug # (if any)	Issue
	Date.toDateString and Date.toTimeString are not implemented.
37333	Some features of signed scripts in Navigator 4.x are not yet implemented in Mozilla or Netscape 6, including <SCRIPT ARCHIVE=> and ID= tags.

Bug # (if any)	Issue
	The following three points are not bugs, but are noted here as an FYI for users and developers:
	1) On Mac OS only, the name of the folder for installing plug-ins is "plug-ins" with a hyphen (for backward compatibility with Communicator 4.x for the Mac and legacy plug-in installer binaries), not "plugins" as on Windows and Linux.
	2) On Windows only, if RealPlayer, Flash, or Acrobat are installed in the Communicator 4.x plugins directory but are not installed in the Netscape 6 plugins directory, Netscape 6 will load these plugins from the Communicator 4.x plugins directory. For other plug-ins, and on other platforms, either: rerun the installer for the plug-in, instructing it to install into the Netscape 6 plugins directory (which is named "plug-ins" on Mac only), or copy the files for that plug-in over from the Communicator 4.x plugins directory into the Netscape 6 plugins directory (which are both named "plug-ins" on Mac only)
	3) If a legacy Communicator 4.x plug-in binary is installed within Mozilla or Netscape 6, its basic features will function as expected because of the backward compatibility of the Mozilla Plug-in API supported by Netscape 6. However, if the plug-in has a Java API callable from JavaScript via LiveConnect, these calls within will fail silently until the plug-in binary is upgraded to support the Mozilla Plug-in API. Contact the plug-in vendor to determine when an upgraded plug-in binary will be available for download.
	(Mac OS) QuickTime movies are not displayed correctly, and are offset on the page.
	(Mac OS) If you are watching a Flash or QuickTime movie and you open the Preferences dialog or perform other tasks in which dialog boxes appear, the dialog boxes appear blank. To correct this problem, close the page you are viewing and then perform your task.

Bug # (if any)	Issue
	Netscape 6 includes Java 2 Standard Edition (J2SE) Runtime Environment v1.3.1_01. This release of J2SE was created specifically for support of Netscape 6. Installing Netscape 6 will not disrupt other Java Runtime Environments you may have installed (for instance, JRE 1.3.1, 1.3, or JRE 1.3.0_01 downloaded from java.sun.com). This is the same release that's available from Sun.
	Netscape 6 has been tested only with J2SE v1.3.0_01. Other J2SE releases, or previous JDK's from Sun, will not work with Netscape 6.
	(Mac OS only) You must have Mac OS Runtime for Java (MRJ) version 2.2 to run Java aplets with Netscape 6. If you have Mac OS version 8.5 through 8.6, you may need to upgrade your version of MRJ. For an upgrade, go to the Apple software download pages.
	Running J2SE in Netscape 6 in 256 color mode may cause a flicking problem.
	(Linux) Netscape 6 on Linux and Solaris includes includes J2SE v1.3.0_01. The Java support on Linux and Solaris is not complete (for instance, LiveConnect is not yet enabled), but will be functional in a later release.

Bug # (if any)	Issue
46318	XP Install: Malformed XPI javascript install triggers may cause the installation to hang until the browser's "Stop" button is pressed (or prevent installation entirely on Linux). The correct syntax, which does not cause a hang, is: InstallTrigger.install( {"pretty name": "url"} );