Open
Bug 342118
Opened 18 years ago
Updated 2 years ago
Mouse Event stop firing when leaving browser window under certan conditions
Categories
(Core :: DOM: Events, defect, P5)
Tracking
()
NEW
People
(Reporter: dudrenov, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060608 Ubuntu/dapper-security Firefox/1.5.0.4 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.4) Gecko/20060608 Ubuntu/dapper-security Firefox/1.5.0.4 Mouse event won't fire when mouse leaves window, but only and when the event was initialized on during function call caused by event by element that has no content or element and has text content and you have clicked the actual content. If this does not make sense which I'm sure it does not please take a look at this url: http://www.dudrenov.com/tests/argh.html Reproducible: Always Steps to Reproduce: 1. go to http://www.dudrenov.com/tests/argh.html 2. read instructions. 3. drag elements Actual Results: some of the elements won't reposition when mouse leaves window element Expected Results: element reposition when mouse is moving outsite of browser window
Updated•18 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•18 years ago
|
Assignee: nobody → events
Component: General → DOM: Events
Product: Firefox → Core
QA Contact: general → ian
Version: unspecified → 1.8 Branch
I shoudl update this bug since I posted it. Furder tests show that this happens only if I prevent the default action on mouse down which cause the browser not to select any text. Or if I put -moz-user-select: none; on the element. IF none of those is present executed then it's fine.
Updated•15 years ago
|
Assignee: events → nobody
QA Contact: ian → events
Comment 2•6 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•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•