Closed
Bug 11518
Opened 25 years ago
Closed 25 years ago
[TRACKING]onmouseover with <AREA> not firing
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: buster, Assigned: dbaron)
References
()
Details
(Keywords: meta, testcase)
Attachments
(1 file)
(deleted),
text/html
|
Details |
something is broken on this page related to javascript. The image on the lower left has a label underneath it which is suppose to change as you mouse over the blue dots. Furthermore, several of the blue dots have mouse-over behavior to show/hide green dots. These do not show up either.
Comment 1•25 years ago
|
||
Updated•25 years ago
|
Whiteboard: [TESTCASE]
Assignee | ||
Updated•25 years ago
|
Assignee | ||
Comment 2•25 years ago
|
||
I filed bug 12152, bug 12154, and bug 12155 on this page. I'm marking the first two as dependencies of this one. It's not clear that the first, bug 12152, is a problem here, but it might be. I hit it creating a simple test case (suspecting a totally different problem). The second, bug 12154, definitely is a problem here. The third, bug 12155, deals with the slowness of the page's loading in general.
Assignee: vidur → joki
Summary: dynamic content doesn't change as in Nav4 → onmouseover with <AREA> not firing
Event bug, ergo joki? (Can reproduce with today's build on Linux.) I suspect there's a dup out there somewhere, but I can't find it. Updating summary.
Assignee | ||
Comment 4•25 years ago
|
||
This bug was really acting as a tracking bug, since it's not entirely clear if all the other bugs are the problem. You can assign it to me if you don't want to hold on to tracking bugs. (shaver - You just changed the title to make it a dup of bug 12154, which was a dependency, and probably the bug you were thinking of.)
Assignee: joki → dbaron
So I did. If you can take this one and track the dependencies, that'd be great. Reassigning the the L. David Baron conspiracy.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 6•25 years ago
|
||
[monitoring AREA element bugs]
Assignee | ||
Updated•25 years ago
|
Summary: onmouseover with <AREA> not firing → [TRACKING]onmouseover with <AREA> not firing
Comment 8•25 years ago
|
||
Bulk moving [testcase] code to new testcase keyword. Sorry for the spam!
Keywords: testcase
Updated•25 years ago
|
Keywords: meta
Summary: [TRACKING]onmouseover with <AREA> not firing → onmouseover with <AREA> not firing
Whiteboard: [TESTCASE]
Comment 9•25 years ago
|
||
Nominating nsbeta2. Isn't onmouseover really part of DOM0? Not sure why this is marked DOM1. Anyway, regardless of which DOM level this should be considered part of, in terms of importance it's a DOM0 backward compatibility bug. onmouseover is widely used for mouse rollovers and the like.
Keywords: nsbeta2
Assignee | ||
Comment 10•25 years ago
|
||
This has become a tracking bug since there were multiple issues in the page. Both dependent bugs are already marked nsbeta2, so I'm removing the nsbeta2 here. (Also, changing to DOM0 and marking [TRACKING] in summary.) Furthermore, the original URL has completely changed, so the only reason to keep this open is to verify the testcase, which seems to me to work just fine despite the dependent bugs still being open.
Component: DOM Level 1 → DOM Level 0
Keywords: nsbeta2
Summary: onmouseover with <AREA> not firing → [TRACKING]onmouseover with <AREA> not firing
Assignee | ||
Comment 11•25 years ago
|
||
Actually, I'm going to mark this as WORKSFORME because the testcase works fine, the original URL has changed, and all the problems detected before on the original page and testcase are filed as separate bugs.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•