19964 - msu.edu - [LAYER] <Div> Mouseover isn't working

Status: VERIFIED WONTFIX

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

Description

[bryans]

If you go to the page listed above with Netscape and move your mouse over the
"Coasters, Rumors, Virtual Coasters" ETC. you see a division appear in the upper
left hand corner. With Mozilla, none of the division appear. I'm not sure how
far along the Javascript engine is, but this is just something that I noticed.
-Jason Bryans

Comment 1

[Mike McCabe]

Transferring to the DOM component.

Comment 2

[Robert Ginda]

Changed QA Contact to Prashant

Comment 3

[vidur (gone)]

In an attempt to get my bug list in order again, marking all the bugs I have
currently as ASSIGNED.

Comment 4

[Kevin McCluskey (gone)]

The mouseover is indeed working. The following error is spit out when mousing
over. Looks like its having problems accessing a property on an array of
documents that are initialized in the function setupBrowser().

Document file:///S|/mozilla/dist/WIN32_D.OBJ/bin/res/samples/demo.html loaded su
ccessfully
Document: Done (2.794 secs)
JavaScript Error: TypeError: divStyle[i] has no properties
URL: file:///S|/mozilla/dist/WIN32_D.OBJ/bin/res/samples/demo.html
LineNo: 33

Comment 5

[vidur (gone)]

Actually a LAYERs issue - the positioned DIVs in this page got translated to
layers in 4.x. Since all layers with IDs were exposed as document properties,
they could be accessed directly off the document (e.g. document.d0, document.d1,
etc. in this example). Furthermore, scripts could modify their top, left and
visibility properties.

The analogs in the DOM Level 1/2 is to use document.getElementById() to access
the named DIVs (e.g. document.getElementById('d0')) and to (as in IE) modify the
top, left and visibility of the style property of the element (e.g.
document.getElementById('d0').style.top = '3px';).

I'm going to keep this bug open rather than invalidate it - it would take little
work to rig up enough compatibility to get the example to work. In talking to
Eric Krock, it seems like a good plan is to make more headway into the DOM bugs
and issues and, at some later post-Beta date, decided whether or not to try to
provide some minimal amount of compatibility.

Comment 6

[vidur (gone)]

The later post-Beta1 date has arrived and it seems that we're sticking with the
decision to not support non-DOM-sanctioned positioning APIs. I'm marking this
bug WONTFIX.

Comment 7

[ekrock's old account (dead)]

That's the right decision. Permanent WONTFIX.

Comment 8

[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 9

[ekrock's old account (dead)]

Reopening to register fact that this page probably 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.

Comment 10

[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 11

[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 12

[Blake Ross]

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

removing the now-depreciated evangelism-related keywords.

setting platform to All.

Comment 13

[Blake Ross]

Reassigning evangelism bugs to [e-mail].

Comment 14

[Zach Lipton [:zach]]

The reporter is the owner if the site. Reporter: if you are still listening,
your site needs to be updated to use standards. Bc: can you give a better
description as to what needs to be changed?

Thanks

Zach

Comment 15

[Bob Clary [:bc] (inactive)]

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

Comment 16

[z-aillon.c-obsolete2]

SPAM.  You may filter these bugs by querying the string "ReadingRitingRithmetic"

Mass Moving Bugs on Educational institutions in the United States to the new US
Edu component and assigning to default owners.

Comment 17

[Pascal Chevrel:pascalc]

Should this bug be closed now ? This page hasn't been updated in 2 and a half
years, this was a personal page led by a high school student :

"Q. Why is your page on MSU.edu? Are you a college student there?

A. Ok, I work at MSU technically as a student employee, but I am not a student
there. I acually go to school at the local high school. So why do I have an
account? It's my parents, they work at MSU, they are computer illirate, so I
might as well use it."

I believe that it is very unlikely that this page will ever change and anyway,
the problem was just a cosmetic glitch.

Comment 18

[bryans]

Problem is caused by non-complient div coding, problem has already been resolved
withing Mozilla - not a problem with Mozilla itself. 

Comment 19

[Brant Gurganus]

not fixed

Comment 20

[Brant Gurganus]

from page owner via AIM:
Chetchez: I probably won't update that site, however - I did use the code and
re-work it and made it compatable with Mozilla (Link:
http://mason.k12.mi.us/)http://mason.k12.mi.us/ The blue bars use almost the
same code.

Comment 21

[Brant Gurganus]

verified by actual contact by AIM

Comment 22

[Bob Clary [:bc] (inactive)]

tech evang june 2003 reorg