When I went to http://cws.internet.com/new.html, the Mozilla browser started to render the page, but it seemed to stop responding. The scroll bar appeared, but there were no arrows on it. This also happened, to a lesser extent (the page eventually appeared) at browserwatch.internet.com/news.html and your own Bugzilla Bug report form. I am using the 3/29/99 build of Mozilla with apprunner.

This sounds very much like bug #4387. See the discussion there between troy and pollman (who apparently has just checked in a fix). Dup?

I copied the above url locally, added <BASE href="http://cws.internet.com/new.html"> to the head and removed all of the javascript. The page took a very long time to load. I then removed the <link rel = STYLESHEET href = "java/style.css" type = "text/css"> and the page loaded much faster. I'm changing the component and reassigning to Peter.

I don't know if the source page changed or what... but this page currently has problems loading after a document.write() FWIW: the stylesheet seems to be loading fine.

There is a javascript problem (which I saw in another bug and assigned to Vidur, but didn't report here). But after removing the javascript from this url, the presence of the external style sheet causes a noticeable performance degradation.

Moving to M6 for now.

The page seems to load fine, but there are severe problems with layout. There's a pretty high dependence on correct layer layout (the menu on the left is done using layers in Nav). Needs a lot more investigation, but I'm pushing this off to the layer pile.

Putting on [Perf] radar

Assigning all layers bugs to ekrock.

Setting all LAYER bugs to M15 for as-time-allows evangelism.

With the latest NECKO builds on 08/05, the page seems to have no trouble loading, but the layout problem still exists as vidur mentioned earlier.

Vidur--to confirm: bugs should only be assigned to my [LAYER] (e.g. "Layer API") pile if they are a result of the Nav4 Layer DOM API (document.layers, etc.) being used in JavaScript. If we are not laying out static HTML LAYER tags correctly, then that should be filed as a layout bug as we are signed up to lay out LAYER tags correctly. I haven't had time to look at this page yet, but since you have already--if this is a document.layers usage issue, please leave assigned to my pile; if it's a LAYER tag not laying out correctly issue, please reassign to whoever lays out LAYER tags. Thanks!

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

Marking verified invalid per last comments.

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.

Reopening to register fact that this page isn't yet upgraded (until it is, at which point we'll close the bug). Clearing cc:s as a courtesy to reduce spam.

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.

Site seems to be fixed, and layers are no longer used.

verified

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