Status
()
People
(Reporter: erik, Assigned: joki)
Tracking
Firefox Tracking Flags
(Not tracked)
Details
(Whiteboard: [TESTCASE] WORKSFORME (27/07/99), URL)
Attachments
(1 attachment)
212 bytes,
text/html
|
Details |
If I have an element with text in the event isn't fired until the text node fires the event. I'll show a short sample: <div style="background-color: yellow; width: 500px; height: 500px;" onmouseover="alert('K.')"> Short text </div> The text node fires the event that is then bubbled to the div node but the div node doesn't fire an event by itself.
Comment 1•20 years ago
|
||
per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
QA contact re-assigned according to the product areas we're currently working on.
(Assignee) | ||
Updated•20 years ago
|
Status: NEW → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED
(Assignee) | ||
Comment 3•20 years ago
|
||
The behavior of mouseover isn't really specified to this level. If I mouseover the text, I'm going to get a mouseover on the text which will bubble up to the div. That's just the way it works at the moment. There was a separate bug where hitting the rest of the div would not cause an event at all. This is fixed now.
(Reporter) | ||
Updated•20 years ago
|
Status: RESOLVED → REOPENED
(Reporter) | ||
Comment 4•20 years ago
|
||
This isn't satisfactory from a dhtml developer point of view. This forces me to fill up the entire container with text which isn't possible (the borders). For example I can't create buttons, toolbars etc that can be clicked anywhere, only at the text. This is almost as bad as when you in NN4.x only provided a background color behind the text in the container!
(Assignee) | ||
Updated•20 years ago
|
Status: REOPENED → ASSIGNED
(Assignee) | ||
Updated•20 years ago
|
Resolution: FIXED → ---
(Assignee) | ||
Comment 5•20 years ago
|
||
No, you still get events on the div. And if you're not keep in mind I only marked this fixed today, the change only went in hours ago. So the deal is over empty space -> event goes to div over text -> event goes to text, bubbles to div. This is the solution.
(Assignee) | ||
Updated•20 years ago
|
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago → 20 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Status: RESOLVED → REOPENED
Comment 6•20 years ago
|
||
Build: 1999-04-26-08 Not fixt. I get no alert for this test. I put the test included in this bug report on http://slip/projects/marvin/bugs/bug_2989.html for easier reference.
Updated•20 years ago
|
Resolution: FIXED → ---
(Reporter) | ||
Comment 7•20 years ago
|
||
The test doesn't use window.alert. It writes out the the text using DOM and it worked with 1999-04-22 (maybe something went wrong during those two days?) I don't see how it becomes more easy when the provided URL doesn't work :-) The old URL is still available at http://webfx.eae.net/gecko/testEvents.html
(Assignee) | ||
Comment 8•20 years ago
|
||
Yeah, noticed the change still in my tree. Must have forgot to check it in. I'll add it when I can.
Updated•20 years ago
|
Whiteboard: [MAKINGTEST] jonesev@home.com (26/07/99)
Comment 9•20 years ago
|
||
Created attachment 1003 [details]
Fires events with a mostly blank DIV tag
Updated•20 years ago
|
Whiteboard: [MAKINGTEST] jonesev@home.com (26/07/99) → [TESTCASE] WORKSFORME (27/07/99)
Comment 10•20 years ago
|
||
It seems to me that the original problem, Blank areas of elements doesn't fire events, is fixed now. I tested the code in the bug description that was created by d96erik@dtek.chalmers.se (and I created a test case for the bugathon) on the daily build for July 26, 1999 on Linux and the blank areas of the DIV fired the onmouseover events. Can anyone else (maybe a Mozilla engeneer?) confirm if this is fixed now?
Updated•20 years ago
|
Status: REOPENED → RESOLVED
Last Resolved: 20 years ago → 20 years ago
Resolution: --- → FIXED
Comment 11•20 years ago
|
||
Marking this resolved-fixed. I think joki checked in the fix sometime between April and now. It sure looks fixed. This bug dealt only with the second test on the page. However: I couldn't find any bugs on the other two tests on the page. The first one is IE-specific syntax that has been replaced in DOM2. The problem in the third test area is a dup of bug 11009 and I will add a note there.
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
(Assignee) | ||
Updated•19 years ago
|
Summary: Blank areas of elements doesn't fire events → [EVENTTARG] Blank areas of elements doesn't fire events
You need to log in
before you can comment on or make changes to this bug.
Description
•