Closed
Bug 9140
Opened 25 years ago
Closed 24 years ago
{html4} AREA elements don't fire events
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Core
DOM: UI Events & Focus Handling
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: luch, Assigned: harishd)
References
()
Details
(Keywords: testcase, Whiteboard: [nsbeta2+])
Attachments
(2 files)
In <map> html command, there used to be the onMouseOver, onMouseOut and others in the definition of <area> tag. On the url submited, there's a menu at the left site that uses roll-overs. When on normal buttons, the top menu image switches to a new one. But when on the "I" button, the browser is expected to make the top image change. Here is the rollover command used on that page: <MAP NAME="haut"><AREA SHAPE=RECT COORDS="8,4,17,13" HREF="main.htm" onMouseOver="anim('1');" onmouseout="unanim();"></MAP> and the image tag which uses that map: <IMG SRC="pitonbas.gif" usemap="#bas" border=0 width=130> I'm using the Milestone 7 Mozilla browser. Hope I didn't forget anything!! Great work guys!
Assignee: mccabe → joki
Component: Javascript Engine → Event Handling
QA Contact: cbegle → janc
Updated•25 years ago
|
Whiteboard: [MAKINGTEST] Antti.Nayha@oulu.fi
Updated•25 years ago
|
Whiteboard: [MAKINGTEST] Antti.Nayha@oulu.fi → [TESTCASE] Events must be implemented on the AREA element
Comment 2•25 years ago
|
||
Attaching a minimized test case & rewriting the bug report in accordance to the guidelines. Overview description: AREA element doesn't fire onMouseOver and onMouseOut events. Steps to reproduce: 1) View the attachment. 2) Move the pointer over and out areas 1-6. Actual results: Nothing. Expected results: Moving in or out from each AREA should produce a JavaScript alert, eg. "Pointer over Area 4" or "Pointer out from Area 2". (Note that tests 4-6 use nonstandard area shapes, but we'll probably want to implement those as well since they are supported by popular browsers.) Build date & platform: - originally reported on Windows 95, build date unknown. Additional builds & platforms: - Apprunner 1999072711 (Windows NT 4.0 SP4) - Viewer 1999072711 (Windows NT 4.0 SP4) - M8 Apprunner (Windows NT 4.0 SP4)
Comment 3•25 years ago
|
||
Updated•25 years ago
|
Summary: <area> tag doesn't support onMouseOver commands → AREA elements don't fire events
Comment 6•25 years ago
|
||
Tested with todays builds. Its still there.
Blocks: 11518
Updated•25 years ago
|
Updated•25 years ago
|
OS: Windows 95 → All
Comment 9•25 years ago
|
||
Still there. I've changed OS to 'All'. I understand that this is quite an important omission, since HTML 4.0 compliance requires support of this feature (I am told).
Updated•25 years ago
|
Hardware: PC → All
HTML 4.0 compliance doesn't require much of anything...
Comment 11•25 years ago
|
||
dbaron: how true, how true... :-( A better way of phrasing it is "This is required for full HTML4 support". Adding relevant dependencies.
Updated•25 years ago
|
Target Milestone: M14
Updated•25 years ago
|
Summary: AREA elements don't fire events → {html4} AREA elements don't fire events
Target Milestone: M14 → M16
Comment 12•25 years ago
|
||
Moving M16.
Comment 13•25 years ago
|
||
Bulk moving [testcase] code to new testcase keyword. Sorry for the spam!
Keywords: testcase
Comment 14•25 years ago
|
||
*** Bug 1427 has been marked as a duplicate of this bug. ***
Comment 15•25 years ago
|
||
*** Bug 25056 has been marked as a duplicate of this bug. ***
Comment 16•25 years ago
|
||
*** Bug 24041 has been marked as a duplicate of this bug. ***
Comment 17•25 years ago
|
||
Comment 18•25 years ago
|
||
There are 12 events that area elements should support according to the W3C Recommendation: http://www.w3.org/TR/html4/struct/objects.html#adef-usemap They are demonstrated in the recently added attachment
Comment 19•25 years ago
|
||
*** Bug 25490 has been marked as a duplicate of this bug. ***
Comment 20•25 years ago
|
||
*** Bug 25776 has been marked as a duplicate of this bug. ***
Comment 21•25 years ago
|
||
*** Bug 26049 has been marked as a duplicate of this bug. ***
Updated•25 years ago
|
Whiteboard: [TESTCASE] Events must be implemented on the AREA element → Events must be implemented on the AREA element
Comment 22•25 years ago
|
||
Nominating for beta 1. Look at the number of DUPs on this one.
Keywords: beta1
Comment 23•25 years ago
|
||
If this has really been moved to beta1 then shouldn't the milestone be set to m14 or m15?
Comment 24•25 years ago
|
||
adding [PDT+]
Whiteboard: Events must be implemented on the AREA element → [PDT+]Events must be implemented on the AREA element
Updated•25 years ago
|
Whiteboard: [PDT+]Events must be implemented on the AREA element → [PDT+]Events must be implemented on the AREA element, fix expected 2/10
Comment 26•25 years ago
|
||
*** Bug 26541 has been marked as a duplicate of this bug. ***
Updated•25 years ago
|
Whiteboard: [PDT+]Events must be implemented on the AREA element, fix expected 2/10 → [PDT+]fix checked in, checking with vidur for full completion status
Comment 27•25 years ago
|
||
Okay, vidur say's he thinks this should fully work now. Resolving fixed
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Whiteboard: [PDT+]fix checked in, checking with vidur for full completion status → [PDT+]
Comment 28•25 years ago
|
||
ondblclick event still doesn't fire. See attachment 4647 [details]. Also, you cannot tab
to area elements (so keypress events cannot be tested), but that, I assume, is a
separate bug.
Comment 29•25 years ago
|
||
I have verified that the ondblclick event does not fire for IMG or A elements so this is a separate bug. This bug is therefore resolved.
Comment 30•25 years ago
|
||
Not fixt. using the attachment http://bugzilla.mozilla.org/showattachment.cgi?attach_id=4647 Win98: 2000021408 - onmouseout creates repeating alert dialog boxes which after efforts to close them crash the browser Linux: 2000021416 - none of the tests work Mac: - ondblclick doesn't work - onmouseout creates repeating alert messages which quickly lock up the program, and eventually crash the system. - onmouseover = same
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 31•25 years ago
|
||
Okay, fixed the repeating alert message problem. The dblclick problem is covered elsewhere. This is as far as this gets for M14. The only remaining problem I see below that would keep this bug open is that part about this not working at all on Linux. This is all xp code though, it really should work. Removing PDT+, moving to M15. If someone with a working Linux build can verify this is still a problem I'd appreciate it with any additional info available. If we can verify this works on Linux this bug should be closed.
Status: REOPENED → ASSIGNED
Whiteboard: [PDT+]
Target Milestone: M14 → M15
Comment 32•25 years ago
|
||
Putting on the PDT+ radar for beta1. But please mark this one fixed and open additional bugs if necessary.
Whiteboard: [PDT+]
Comment 33•25 years ago
|
||
Fine. Since as far as I know this should work fine on linux too i'm just going to mark it fixed then.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
Comment 34•25 years ago
|
||
Reopening bug. I checked it with todays builds [02-24-09]. Not fixed. using the attachment http://bugzilla.mozilla.org/showattachment.cgi?attach_id=1032 Win95: 2000022409 - onmouseout creates repeating alert dialog boxes which after efforts to close them crash the browser Linux: 2000022409 - mouseout event does not fire.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 35•25 years ago
|
||
The linux part of this is known and not a big deal. The Win95 bit is new and the only part of this that might make this PDT+. So is the suggestion here that it only fail on Win95? Since the fix was developed on WinNT I'm asusming it still works there. My build is a day or two old so I'm repulling to check. But can someone verify that?
What's the bug# on the Linux problem?
Comment 37•25 years ago
|
||
I hadn't realized that was a different test case. With the original one it works fine but with the one mentioned it does crash on WinNT as well. I hadn't opened a seperate bug for the linux stuff since the last mention before this said the test case didn't work at all on linux which I was skeptical of and waiting for additional verfication. The most recent comment says mouseout doesn't work which at least indicates the other stuff works. That still seems a little odd to me, though. it would be interesting to rewrite this test with 'dump' instead of 'alert' and see what happens.
Comment 38•25 years ago
|
||
Can we have an update, and a planned landing date? I'm adding the comment to the status whiteboard that we'll have to PDT- this on 3/3. Time is running out...
Whiteboard: [PDT+] → [PDT+] w/b minus on 3/3
Comment 39•25 years ago
|
||
Okay, I have worked out a fix that doesn't scare me at all like a couple of others did.
Whiteboard: [PDT+] w/b minus on 3/3 → [PDT+] w/b minus on 3/3, simple fix in hand
Comment 40•25 years ago
|
||
*** Bug 19178 has been marked as a duplicate of this bug. ***
Comment 41•25 years ago
|
||
Okay. I've checked in a fix for the most recent problem, that of window level mouseover events which were actually occurring over the alert box constantly triggering the mouseexit handler direclty beneath the alert and causing a loop. I'll need to fix this a bit more later by differentiating these two types of events so we don't get them in content but that's a larger fix and can wait for post-beta. Removing pdt+, removing beta1.
Comment 42•24 years ago
|
||
this was working before, but on the latest build, seems to be gone (at least for netscape.com)
Comment 44•24 years ago
|
||
adding beta2 keyword, and removing pdt status
Keywords: beta2
Whiteboard: [PDT-]
Comment 45•24 years ago
|
||
removing beta1 keyword so it doesn't show up on beta1 radar
Keywords: beta1
Comment 46•24 years ago
|
||
Mass-moving bugs out of M15 that I won't get to. Will refit individual milestones after moving them.
Target Milestone: M15 → M16
Comment 47•24 years ago
|
||
PDT would like a retest with latest build please. Thanks!
Keywords: beta2
Whiteboard: [RETEST NEEDED]
Filed crash bug on second testcase as bug 37479. Some of the events in that testcase still don't work. However: * some of them shouldn't work (key/focus events) * For the ones that don't, do they work on other elements? (I don't know.) If they don't, are appropriate bugs filed?
Comment 49•24 years ago
|
||
using attachment 4647 [details]:
ondblclick doesn't work on any platform
onmousemove locks up the browser on the mac
2000-05-05-08-M16 Win32
2000-05-05-13-M16 Linux
2000-05-05-10-M16 Mac
Comment 50•24 years ago
|
||
Removing [RETEST NEEDED] for PDT re-eval ...thanks!
Whiteboard: [RETEST NEEDED]
Comment 51•24 years ago
|
||
*** Bug 28858 has been marked as a duplicate of this bug. ***
Assignee | ||
Comment 53•24 years ago
|
||
Taking from Joki for analysis.
Assignee: joki → harishd
Status: ASSIGNED → NEW
Assignee | ||
Comment 54•24 years ago
|
||
All events except "onDblClick" [ 06/13/00 build ]. And "onMouseMove" did not lock up mac [ 06/12/00 build ]. Jan, could you verify this? Thanx.
Assignee | ||
Comment 55•24 years ago
|
||
All events except "onDblClick" [ 06/13/00 build ] work. And "onMouseMove" did not lock up mac [ 06/12/00 build ]. Jan, could you verify this? Thanx.
Comment 56•24 years ago
|
||
Checked this out on MacOS9 2000-061908-M17 build and all events except dblclick and onselect work. Harish, check out http://voodoolady/events/mousies for testcases related to mouse and key events. I'll try to post those to an external website as well for folks outside the firewall...
Assignee | ||
Comment 57•24 years ago
|
||
From ckritzer's comment I understand that we don't freeze on MAC anymore. Events not working: OnSelect ( Ref. Bug 4033 ) OnDblClick (Ref. Bug 29473 ) Tom, what should we do with this bug?
Assignee | ||
Comment 58•24 years ago
|
||
Okay, the bug seems to be fixed. Btw, OnSelect is not supposed to work on IMG maps...and onDblClick will be dealt as a different bug ( probably 29473 ). Closing the bug.
Status: NEW → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → FIXED
Comment 59•24 years ago
|
||
I'm going to verify this bug with the note that there are still a couple of things happening wrong. I think they are new bugs, so I'm going to write them up in a new bug and ref this bug in it. 2000-07-12-11-M17 : Linux onMouseOver brings up 2 alert boxes 2000-07-12-13-M17 : Mac onMouseout & onMouseOver bring up 2 alert boxes 2000-07-12-09-M17 : WinNT & Win98 Verified (onDoubleClick is indeed covered on bug 29473)
Status: RESOLVED → VERIFIED
Updated•5 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•