the font styles are not displaying. They are kept in an external style sheet (detect.js) written in javascript (browser sniffer implemented and font styles assigned to each browser)

-> Style System. Could be a dup (I seem to remember reading about this in some comments somewhere). Gerv

dup of 29370?

Yes, dup of 29370. Disable the Mem Cache in the Debug prefs or try a more recent M15 build. *** This bug has been marked as a duplicate of 29370 ***

Maybe that bug should not have been closed as dup. <crawdad@io.com> wrote in bug 29370: ---- I think bug 32704 is just bad browser detection, nothing to do with caching, that I can see.. just plenty of .layers/.all code. ---- We have 2 problems there as far as I can tell: - Some garbled characters below the scrolling view: could be a dup of bug 27223. - The 2 menus ("B2BXchange" and "Internet Services..." don't work: could a dup of bug 20867. Anyhow, I'm reopening.

This is a dup of bug 27223. As <crawdad@io.com> pointed out, it's a problem with layers and browser sniffing and like 27223, I'm reassigning to ekrock to evangelize the webmaster. IMPORTANT - this may be a BIG problem - the 2 pages on http://www.virtualfund.com/newvfnd/ (this bug) and http://www.agn3d.com/html/agn3d-nav2.html (bug 27223) have very similar code. They both import the same javascript file: <script language="JavaScript" type="text/javascript" src="dynlayer.js"> It means that the problem may not coming from the webmasters themselves but from the development tools they are using to generate their pages.

INVALID. LAYER, ILAYER, document.layers[] not supported in Gecko/Nav5. Closed. Notified reporter and site owner via template at http://sites.netscape.net/ekrock/fixit/layer.html In the future, if possible, please INVALID, notify, and close such bugs directly using that template without assigning to me. Thanks! P.S. dynlayer.js is, I believe, one of the standard free Nav4/IE4 browser-independent DHTML stub function libraries. I've emailed the developers of many of those libraries asking them to add support for the W3C DOM.

Adding 'verifyme' keyword

Verifying INVALID.

Moving all [LAYER] bugs to Evangelism component for tracking and open-source evangelism by mozilla community members of sites that need to upgrade to support web standards such as HTML 4.0 (instead of LAYER/ILAYER) and the W3C DOM (instead of Nav4 document.layers[] or IE document.all()). Sites should be lobbied to do the upgrade using the email templates that are linked to from http://www.mozilla.org/newlayout/bugathon.html#layerbugs . When a site's owner has confirmed receipt of the message requesting an upgrade, the bug should be marked with the keyword evangelized to indicate that evangelism for that bug is complete. When the site finishes the upgrade and supports standards, the bug should be closed.

Marking bug evangelized and clearing cc:s.

SPAM:Changing QA contact on 111 evang bugs as I am now the new QA contact for this component. Sorry about the spam zach

Reassigning Evangelism bugs to me, the component's new owner. I would like to take this opportunity to thank nobody@mozilla.org for all of his dedication, contributions, and hard work, and wish him luck at his new job. Thanks, nobody.

Removing the evangwanted keyword from 49 evangilizm bugs that also have the evangelized keyword. Having both of these keywords on a bug makes it really hard to do a query for all open evangilizm bugs that are evangwanted. Sorry for the spam.

-> evangelism@telocity.com for my evangelism bugs. removing the now-depreciated evangelism-related keywords. setting platform to All.

Reassigning evangelism bugs to bclary@netscape.com.

All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for details.

site now works (even mentions ns6)

Verified 2002040303/WinXP