202856 - mistaken second mousedown event fired on absolute positioned div

Status: RESOLVED WORKSFORME

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[dh]

User-Agent:       Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020623 Debian/1.2.5-0.woody.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030401

In the test case, begin a drag within the div to create a block, as intended,
completing your drag within the borders of the div.  Now drag outside of the div
to mistakenly create another block within the div.  This should not have
triggered the mousedown on the div.  It only manifests itself once.  Beginning a
second drag outside of the div does not trigger the mousedown on the div a
second time.

However, begin a drag within the div to create a block and complete the drag
beyond the border of the div.  Now dragging outside of the div does not trigger
the erroneous mousedown event on the div.

Mozilla does not exhibit this behavior without absolute positioning.


Reproducible: Always

Steps to Reproduce:
1.begin drag within the rectangle
2.complete drag within the rectangle
3.begin drag outside of the rectangle to mistakenly fire eventListener on rectangle

Actual Results:  
mozilla created a block in the rectangle that it shouldn't have created

Expected Results:  
dragging outside of the rectangle should do nothing.

This may be very specific, but it may be a show-slower for a calender
application I'm developing.  "Click to create" is a powerful feature.

Thank you for mozilla!  Bugs and all, I love it!

Comment 1

[dh]

Attachment: Errant mousedown test

Comment 2

[Boris Zbarsky [:bzbarsky]]

This seems to work for me with linux trunk build 2003-04-12-22 -- dragging
outside the rectangle has no effect....

Comment 3

[dh]

It's true.  The nightly build for Linux for April 21 handles it properly too. 
My apologies.  The test case was for 1.4a.  (Allright!  Go mozilla!!)

Comment 4

[Boris Zbarsky [:bzbarsky]]

Good to hear.  ;)

Marking worksforme, but please reopen if this problem reappears...