20737 - [LAYER] remove all I/LAYER-aware code from Mozilla

Status: VERIFIED FIXED

(Tech Evangelism Graveyard :: English US, defect, P1)

Description

[Richard H Ponton Jr]

Sorry for the lack of specifics.

Using Mozilla M11, I went to www.zdnn.com (redirected to www.zdnet.com/zdnn) and
the page is completely mangled.  It shows up fine in Netscape 4.xx on both
Windows and Linux.

Comment 1

[Mats Palmgren (inactive)]

This site uses LAYER/ILAYER but would look OK if Mozilla actually behaved as
http://sites.netscape.net/ekrock/standards.html
describes, but it does not (yet).

Comment 2

[ekrock's old account (dead)]

Mats--Are you sure? If so, please explain.

After investigating with my test cases, as far as I can tell Mozilla is behaving
as that document says. If that's true, please close this as a DUP of the ZDNet
bug. Thanks!

Comment 3

[Mats Palmgren (inactive)]

Attachment: testcase

Comment 4

[Mats Palmgren (inactive)]

I have attached a copy of http://www.zdnet.com/zdnn/ where I have renamed all
LAYER tags to XLAYER and all ILAYER tags to XILAYER. As you can see it is
laid out quite differently than the original. The problem is that (as far as
I can tell) the attributes of LAYER/ILAYER isn't ignored as they should. This
is why the original is shifted out of the viewable area to the right. I think
it is caused by the attributes: LEFT, TOP and WIDTH still being recognized.
I said it "would look OK" eventually but perhaps that was an overstatement.
But at least the content will be viewable (as you can see from the testcase).
(BTW, the testcase crashes occasionally - it's a known bug in ImageLib that
 hopefully will be fixed soon)

Comment 5

[leger]

Updating QA Contact.

Comment 6

[ekrock's old account (dead)]

Mats--YOU ARE THE MAN! Mats is correct that Mozilla is not treating I/LAYER as
unknown tags. It turns out that the changes agreed to earlier haven't been put
into place yet. Vidur has kindly agreed to take the bug. Here are the needed
changes:

1) in html.css, LAYER and ILAYER must be removed
2) in the HTML content sink, we must remove the code which creates special
content for LAYER and ILAYER
3) in the parser, we must remove LAYER and ILAYER from the element table

When these three changes have been made, I expect that this bug will be fixed.

Mats discovered that Mozilla laid out the page differently when the LAYERs were
changed to XLAYERs and the ILAYERs were changed to XILAYERs. I confirmed this
and will attach two more test cases to this bug.

Fixing this bug should be our highest post-dogfood priority as the existence of
this bug is blocking ZDNet (and other sites) from upgrading their sites to
support Mozilla (while keeping backward compatibility with Nav4--a must). ZDNet
has a resource currently assigned to do this upgrade, and we don't want to hold
them up.

Marking M13 but hoping for a fix much sooner.

Comment 7

[ekrock's old account (dead)]

Attachment: layer/ilayer version of the same file

Comment 8

[ekrock's old account (dead)]

Attachment: same file with LEFT, TOP, WIDTH, HEIGHT attributes removed from I/LAYERs

Comment 9

[ekrock's old account (dead)]

Marking [TESTCASE]. After bug is fixed, all three test cases should have the
same appearance. (They'll still look ugly as the files aren't Mozilla-optimized,
but they should all look ugly in an identical way.) Also changing status to
ASSIGNED per Vidur's verbal agreement.

Comment 10

[ekrock's old account (dead)]

Marking M12 as target to unblock ZDNet. Will ask permission from chofmann.

FYI here's the original decision email. Note that it mentions ua.css, not
html.css:

Functionality:
1) LAYER, NOLAYER, ILAYER markup will be
preserved on read-in and write-out.
2) The W3C DOM1 will expose all three elements
and their attributes through the DOM1 methods.
3) LAYER, NOLAYER, ILAYER will be treated
as inline elements in CSS. They will not be rendered
(display:none) but their contents will be rendered.

4 code changes:
a) In ua.css, need to strip out current markup.
b) In content sink, need to create generic content
for these elements.
c) Need to eliminate special-case handling of
NAMEd elements (Vidur knows about this).
d) Need to let NOLAYER pass through parser.

Comment 11

[vidur (gone)]

Fixed on 12/14/1999.

Comment 12

[Chris Petersen]

With the Dec 15th build, this problem has been fixed.

Comment 13

[ekrock's old account (dead)]

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.

Comment 14

[ekrock's old account (dead)]

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.

Comment 15

[Zach Lipton [:zach]]

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

Sorry about the spam

zach

Comment 16

[Blake Ross]

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

Comment 17

[Blake Ross]

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

Comment 18

[Blake Ross]

-> [e-mail] for my evangelism bugs.

removing the now-depreciated evangelism-related keywords.

setting platform to All.

Comment 19

[Blake Ross]

Reassigning evangelism bugs to [e-mail].

Comment 20

[Bob Clary [:bc] (inactive)]

page displays identically in Mozilla/IE5 including link rollover effects.
marking fixed.

Comment 21

[Ian Tommins ('thelem')]

verified.

Comment 22

[Bob Clary [:bc] (inactive)]

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