10618 - [LAYER] Problem with JS image mouseovers using layers.

Status: VERIFIED WONTFIX

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

Description

[ayresp]

HI! its me again! :)
if you visit http://ayresp.hypermart.net/mozilla - you will see 3 buttons and a
img in the left of the screen. IF you pass the mouse Over (onMouseOver) some
button, it change the img. The bug is, if you pass the mouse in none buttons in
the right of the screen, the JS engine consider it as a button, and change the
image.

X-man

Comment 1

[Mike McCabe]

Does this work in 4.x?  It's not at all clear what is supposed to be happening.

Comment 2

[cbegle]

x-man,

please append comments to the bug report so that information does not get lost.
thanks.

X-Man says:
>  Does this work in 4.x?  It's not at all clear what is supposed to be
happening.

In netscape 4.x (i use 4.61), it doesnt work too. In netscape 4.5 the bug is
more powerfull: he doesnt understend the layers position (because of the image)
- mozilla fixed this bug and netscape 4.x doest change the img - just the last
button (if you pass the mouse over de first button, it changes the last button)
- fixed in mozilla in mozilla (milestone 8), the JS enginer and HTML enginer
work very good. you see in this HP a X image and 3 buttons (the
arein portuguese - sorry :). If you pass the mouse over a button it changes the
img, if you pass the mouse over another
img its changes another img and etc. The problem is, if you pass the mouse in
any img (top=50 left=250 - example) the
img changes. But if you pass the mouse over in top=50 left=0 the img doesnt
change - its corect. this bug happens only
in the right of the screen

did you understend?

Comment 3

[cbegle]

event handler thing

Comment 4

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

I think this probably shows two bugs: bug 11009 (mouseovers) and bug 12232
(events and visibility=hidden).  Marking as dependencies.  I'm not entirely
sure, though.

Comment 5

[joki (gone)]

So the decision for 5.0 is that we're not doing layers this time around.  That 
includes the fact that we've removed even the primitive layers support 
we had in previous milestone builds (substituting DIV's for layers).  And as 
inline content, this won't work.  For one thing, none of the 'layers' can be 
accessed as properties of the document anymore.  Not sure if there are other 
problems too.

If you rewrite this without layers and still have problems send it back to me.

Comment 6

[WD]

Verified

Comment 7

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

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

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

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

[Blake Ross]

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

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]]

This needs no evang

Comment 15

[Bob Clary [:bc] (inactive)]

This page uses proprietary Navigator 4.x layer dom. References absolute
positioned divs using document.id where is is the id for the absolutely
positioned div. You can see the error messages in the javascript console. 
Marking priority down though.

Comment 16

[Bob Clary [:bc] (inactive)]

This site uses proprietary navigator 4 dom. The reporter can visit
http://www.mozilla.org/docs/web-developer/ or
http://developer.netscape.com/evangelism/ to see technigues for supporting
Mozilla in a standards based fashion.

marking won't fix.

Comment 17

[Ian Tommins ('thelem')]

Verified. This page was designed as a testpage only.

Comment 18

[Bob Clary [:bc] (inactive)]

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