Closed
Bug 226894
Opened 21 years ago
Closed 16 years ago
onMouseOut not invoked when moved off of first line of LI
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: erik, Unassigned)
Details
(Keywords: testcase)
Attachments
(1 file)
1.45 KB,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031116 Firebird/0.7+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031116 Firebird/0.7+ There may be other ways to reproduce this, but this one is what caught my attention. The onMouseOut event is not firing when the mouse is moved out of the first line of an LI that has had it's display style changed. If you move the mouse upward or downward out of the block, the event fires. If you move past the first line, then move the mouse left or right, it fires. If you move the mouse left or right on the first line, it doesn't fire. Reproducible: Always Steps to Reproduce: 1. Load a page with the attached HTML/JavaScript 2. Move the mouse pointer over the "Test" element, which will cause another UL block to be unhidden like a drop-down menu. 3. Move the mouse downward to the first line that says "Stop Here" 4. Move the mouse left or right off the edge of the element. Notice that the block does not hide. Move the mouse back, then off again, and the block hides. Move the mouse back and then up or down off the element and the block hides. Actual Results: The onMouseOut event does not fire. Expected Results: The onMouseOut even should have fired.
Reporter | ||
Comment 1•21 years ago
|
||
This code provides a suitable environment in which to verify the bug
Reporter | ||
Comment 2•21 years ago
|
||
Correction to the "Steps to reproduce". Step 3 says the element is labeled "Stop Here" but is actually labeled "Test".
This now WFM LInux 2004101106
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 5•20 years ago
|
||
This is still broken, at least on XP, and I don't think this is implementation specific, so it needs to be readdressed. To verify, move the mouse over the Test item, then move the mouse down over the newly revealed test item, then move the mose off to the left or right (making sure not to move back over the orignal elements at the top).
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
"still" using what build?
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 20 years ago
Resolution: --- → WORKSFORME
Reporter | ||
Comment 7•20 years ago
|
||
I thought it was pretty obvious that I was referring to 1.0 Final. If you intend to simply ignore this bug, then please just say that. Otherwise, please stop closing it. This and bug 226895 are essentially the same bug. Between the two of them you can clearly see that there is a problem here with the way the onmouseout event works.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 8•18 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060531 Minefield/3.0a1 This bug seems to be resolved. WFM at least. see also my additions to bug 226895.
Comment 9•16 years ago
|
||
->WORKSFORME
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago → 16 years ago
QA Contact: ian → events
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•