Closed
Bug 302157
Opened 19 years ago
Closed 19 years ago
The onMouseUp event fails to fire in some rather specfic situations
Categories
(Firefox :: General, defect)
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: ondras, Unassigned)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
|
915 bytes,
text/html
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 The onMouseUp event fails to fire, when left mouse button is released on element, while being previously pressed on other element, which might be absolutely positioned. Visit the demonstration page (http://ondras.praha12.net/bug.html) for better understanding. Reproducible: Always Steps to Reproduce: 1. create onMouseUp event for some element (addEventHandler works the same way) 2. create some rather complicated DOM structure, see http://ondras.praha12.net/bug.html 3. press mouse button down on an element, move to another (the one with onMouseUp attribute set) and release. Based on the starting element, sometimes nothing happens. Actual Results: nothing :) Expected Results: An event should fire, for example showing a dialog box (see http://ondras.praha12.net/bug.html) This happens both in 1.0.4 and 1.0.6. It was reported that DeerPark Alpha2 is ok, but I haven't found this bug anywhere, so I'm posting it.
| Reporter | ||
Comment 1•19 years ago
|
||
Comment 2•19 years ago
|
||
WFM Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050725 Firefox/1.0+ ID:2005072519 Using a trunk build, onMouseUp events fire as expected.
Comment 3•19 years ago
|
||
reporter, can you please try this with Deer Park Alpha 2 (Firefox 1.5 alpha) to make sure that this bug has been fixed? Then it can be closed RESOLVED WORKSFORME.
Keywords: testcase
Comment 5•19 years ago
|
||
RESOLVED WORKSFORME as per comment 4
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•