433356 - FF 3 sends a mouseup event when using selecting using a select control; FF2 doesn't.

Status: UNCONFIRMED

(Core :: DOM: Events, defect, P5)

Description

[Jeff Muizelaar [:jrmuizel]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b5) Gecko/2008032620 Firefox/3.0b5

The third calendar on http://www.mattkruse.com/javascript/calendarpopup/ labeled 
"Default calendar using the DIV-style display, with navigation drop-downs enabled." disappears when selecting a month other than May.

This effects various sites such as intervalworld.com that use the calendar control from the mattkruse.com site.


Reproducible: Always

Steps to Reproduce:
1. Click "select" for the calendar with navigation drop downs
2. Choose a month other than the current one from selection box
Actual Results:  
Calendar disappears

Expected Results:  
Month is changed. Calendar stays up.

The calendar control appears to rewrite innerHTML in the onChange event handler. When selecting a month, Firefox 3 fires the onChange event first and then a onMouseUp event which has a originalTarget pointing to the original content instead of the new content from onChange event handler. The original content has a null parentNode because it is no longer in the document. The calendar control code then assumes the onMouseUp event was not inside the calendar control and hides the control.

Obviously, the calendar control makes some poor assumptions so I would understand if this bug was marked WONTFIX. However, is there some place that web authors can go to learn about behavior changes and sites/scripts that are broken and why?

Comment 1

[Jeff Muizelaar [:jrmuizel]]

Attachment: A simple test case that makes the behaviour differences FF2 and FF3 more clear.

Comment 2

[Olli Pettay [:smaug][[e-mail]]]

What FF3 does is right.
FF2 doesn't build event target chain so when <select> is replaced in
change event handler, the already dispatched mouseup can't propagate to
document.
In FF3 where the event target chain is created before event dispatch (per DOM 
Events recommendation), event does propagate up to document.

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

What perhaps could be done is to dispatch 'change' before 'mouseup', not
the current way where 'change' is dispatched while 'mouseup' is being dispatched.
But I don't think that is something we can change in gecko1.9 and that would
change the behavior which has been there forever.

Comment 4

[Wayne Mery (:wsmwk)]

Olli, so this should be confirmed per comment 3?

Comment 5

[Olli Pettay [:smaug][[e-mail]]]

confirmed as wontfix or what?

Comment 6

[Firefox Bug Husbandry Bot]

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.