- [LAYER] Fails to display menu on



Tech Evangelism Graveyard
English US
18 years ago
3 years ago


(Reporter: Phil Peterson, Assigned: bc)






18 years ago
Using 2000-06-26-09 commercial build on NT

1. Go to
2. Hover over "Pro Shop" table cell at upper left

Expected: menu of choices to drop down, as in Nav4 and IE5
Actual: no menu. This site uses the same menu all over the place, and it's
impossible to navigate if this doesn't work

Comment 1

18 years ago
The drop-down menu relies on document.layers, document.all, and fails to detect
Mozilla correctly. See for
details on standards-compliance in Mozilla, and which proprietary features of NS
4.x and IE will not be supported.

Marking INVALID as per
Last Resolved: 18 years ago
Resolution: --- → INVALID
Summary: Fails to display menu on → [Layers] Fails to display menu on

Comment 2

18 years ago
Asa: are you sure?  As far as I could tell from looking at the source, the page 
just uses DIV's that happen to have ID's with "layer" in them.
Component: Browser-General → DOM Level 0
Summary: [Layers] Fails to display menu on → Fails to display menu on

Comment 3

18 years ago
Sorry Asa, you're absolutely right.  The page uses document.all and 
document.layers in an external JS file (menu.js), so I didn't see them when 
initially looking at the source.  vrfy invalid

eric: Nike's a large corporation, and their site's important.  I'll send them 
the standard letter, but is there anything else you wanna do to push them?
Alas, I have no time to do anything on these sites at this point. Marking 
[LAYER] in Summary to enable future evangelism if resources become available.
Summary: Fails to display menu on → [LAYER] Fails to display menu on
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 . 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.
Assignee: asa → nobody
Component: DOM Level 0 → Evangelism
Keywords: evangwanted
QA Contact: doronr → nobody
Reopening to register fact that this page isn't yet upgraded (until it is, at 
which point we'll close the bug). evangwanted. Clearing cc:s as a courtesy to 
reduce spam.
Resolution: INVALID → ---

Comment 7

18 years ago
reassigning back to me to evangelise (am already in contact with Nike's 
Assignee: nobody → BlakeR1234

Comment 8

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

Sorry about the spam

QA Contact: nobody → zach

Comment 9

18 years ago
-> for my evangelism bugs.

removing the now-depreciated evangelism-related keywords.

setting platform to All.
Assignee: blakeross → evangelism
Keywords: evangwanted
Hardware: PC → All

Comment 10

17 years ago
Reassigning evangelism bugs to
Assignee: evangelism → bclary


17 years ago
Summary: [LAYER] Fails to display menu on → - [LAYER] Fails to display menu on

Comment 11

17 years ago
All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for
Component: Evangelism → US English
Product: Browser → Tech Evangelism
Version: other → unspecified
seems to work fine, flash is used (non flash site works fine as well). I see
they have dreamweaver functions that will work with us.
really marking fixed
Last Resolved: 18 years ago17 years ago
Resolution: --- → FIXED

Comment 14

16 years ago
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.