Open
Bug 324251
Opened 19 years ago
Updated 3 years ago
Mousemove events get lost over content area when left mouse button is hold (no select state, using XUL menus in chrome)
Categories
(Core :: DOM: Events, defect, P5)
Tracking
()
NEW
People
(Reporter: mcsmurf, Unassigned)
Details
Recently sometimes i saw the problem that i cannot select menu items in SeaMonkey anymore. This problem normally starts occouring randomly while using SeaMonkey. I clicked on any menu with the left mouse button, held the mouse button and then moved the cursor downwords. Below a certain point menu items would not switch into the selected state anymore, also releasing the mouse button there did not do anyhing. After a bit of testing it turned out that i can select menu items which are displayed over other chrome UI, but as soon as i want to select a menu item which is displayed over content (so normal website display area) this does not work anymore. I cannot reproduce this reliable, but i've seen this bug several times now. For example in the View menu i can select menu items up to "Text Zoom (100%)", but not below.
Suggestions how to provide more debug info are welcome.
| Reporter | ||
Updated•19 years ago
|
Summary: Mousemove events get lost when left mouse button is hold (no select state, using XUL menus in chrome) → Mousemove events get lost over content area when left mouse button is hold (no select state, using XUL menus in chrome)
Yep, I saw this last night on s branch build. I don't know what the steps are to reproduce it, because it happens at random. I'll concentrate on it the next time it occurs.
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a3) Gecko/20060610 BonEcho/2.0a3 ID:2006061009
Updated•16 years ago
|
Assignee: events → nobody
QA Contact: ian → events
Comment 2•7 years ago
|
||
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046
Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.
If you have questions, please contact :mdaly.
Priority: -- → P5
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•