The table with Sponsored Links and such (which is a layer AFAIK) (which displays on the bottom of the page with N4.51) in the viewer app displays at the top of the page overlayed on the rest of the page. In addition the grey table (called Extra according to the image on top of it) is missing. It too is a layer AFAIK. Just compare the page in NS4.51 and viewer, it will be obvious. Viewer dated 1999/4/17. Sorry that I don't know the exact tag that is causing the problem, I'm not yet up to date on layers.

I'm having some trouble duplicating this part, but in addition, I browsed to bugzilla while having the zdnet page displaying first. And it got "stuck". I would see the bugzilla page, then the zdnet page would overlay it. Sometime the bugzilla page would display normally on top, but if I scrolled down I would see the bottom part of the zdnet page still there.

Well, there are a couple of problems here, the most notable of which is that there are ILAYER elements all over the place and we don't support ILAYER

Kipp, the other big problem is that something's wrong with the desired size that's calculated when there are floating tables. This looks like it's related to the change to nsAreaFrame to use the combined-area when calculating the size Here's a small example that demonstrates the problem. If you dump the frame tree, you'll see the floated table has a reasonable height, but the absolutely positioned DIV ends up with a desired height of '0' and nothing is displayed. That's happening quite a bit on this page. <div style="position:absolute; background-color:lightblue; width:200px"> <table align=left width=100> <td>Some text inside of a floating TABLE element</td> </table> </div>

I've fixed the rendering issue with a checkin this morning; the positioning issue still remains.

Well, everything paints now. However, the page is a mess and I'm not sure why. Something to do with an interaction between ilayer and layer and positioning. Back to you troy...

The remaining problems are because we don't support LAYER or ILAYER. We have some very limited support that maps LAYER to 'position:absolute' and maps ILAYER to 'position:relative', but that isn't sufficient

Because Gecko is striving for one 100% CSS1 support and extensive CSS2 support, Gecko should be served HTML that uses CSS rather than layers, if possible

V., Kipp suggested I assign it to you so you can add it to the list of LAYER issues we're collecting

*** Bug 4459 has been marked as a duplicate of this bug. ***

*** Bug 4669 has been marked as a duplicate of this bug. ***

*** Bug 4172 has been marked as a duplicate of this bug. ***

One additional data point: www.zdnet.com is serving different content to the 5.0 user-agent string. You can try 5.0 on a page served to 4.5 at this URL: http://qsilver.queensu.ca/~buslib/4172/www_zdnet_com.html The right hand column appears, but the 'Expand Ad' feature does not work, and there is still a jumble of overlapping tables/layers in the main body of the page.

*** Bug 5200 has been marked as a duplicate of this bug. ***

After adding better support for absolutely positioned elements inside of a relatively positioned inline, things still look bad. In particular, the "SPONSORED LINKS" section is positioned differently. After a lot of effort in tracking down why, I think the problem is a bug in the way Navigator handles LAYER elements nested inside of ILAYER elements. This small example demonstrates the problem: <ilayer>Here's an ILAYER element with a nested LAYER_ <layer width=175 top=100 style="background-color:lightyellow">Text in the nested LAYER. Here's a floated image_ <img align=left width=100 height=100 src="house.gif"> and some text that follows.</layer></ilayer> Here's text after the ilayer. It's displayed inline. Now here's a BR_ <br clear="all">_ that (in Navigator) clears the floated image that's inside the nested LAYER Notice that Navigator is having the BR clear="all" clear the floater that's contained inside of the LAYER element. This is whacky, and doesn't behave the same way in NGLayout. Because the LAYER is moved out of the flow, its floated element has no impact on the flowed elements that follow Anyway, it seems this page is relying on that BR clear="all" element to push "SPONSORED LINKS" to where it's displayed on the screen I don't think that will (or should) ever work in NGLayout

*** Bug 5405 has been marked as a duplicate of this bug. ***

Assigning all layers bugs to ekrock.

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

*** Bug 11303 has been marked as a duplicate of this bug. ***

This problem seems to affect all zdnet subpages as well. Tested under Windows 98 version 4.10.1998 and Mozilla build 1999081711 links table that should be on bottom appears over page content.

INVALID. LAYER, ILAYER, document.layers[] not supported in Gecko/Nav5. Closed. Notified reporter 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! *** This bug has been marked as a duplicate of 2550 ***

Marking as verified duplicate of 2550.

Marking as verified duplicate of 2550.

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.

Closing all Evangelism bugs where no evangelism is needed because page has been fixed, site is internal to Netscape, report is a DUP, or bug report is no longer appropriate for evangelism for any other reason.

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.

workaround bugzilla problem that caused a bunch of evangelism bugs to be NEW/INVALID, NEW/FIXED, NEW/WORKSFORME or NEW/DUPLICATE

re-resolving as dup *** This bug has been marked as a duplicate of 2550 ***

verified

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