567139 - Issue with DOM manipulation (blockUI or alert()) during a onchange request - prevents other event from firing.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[jfrobishow]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100513 Firefox/3.6.4 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.4) Gecko/20100513 Firefox/3.6.4 ( .NET CLR 3.5.30729)

First I thought it was a code issue but it's easy to replicate.  For sample code go to: http://stackoverflow.com/questions/2783479/issue-with-dom-manipulation-blockui-or-alert-during-a-onchange-request-prev

An onchange event with an alert seems to be cancelling the onclick event that follow.

Reproducible: Always

Steps to Reproduce:
1.Read my answer to my own post with explanation and sample code.
2.Live example: http://gutfullofbeer.net/so.html 
3.
Actual Results:  
The onclick event is cancelled

Expected Results:  
The onclick event should have fired.

It seems to be a problem across all browsers (Chrome, IE and Firefox).

Comment 1

[Tyler Downer [He/Him]]

Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html

Comment 2

[jfrobishow]

@Tyler - Triage. 

Yes the issue is still present when using Firefox 3.6.13 in safe mode.

Comment 3

[Tim (fmdeveloper)]

(In reply to comment #0)
> 
> It seems to be a problem across all browsers (Chrome, IE and Firefox).

If it fails in all browsers, are you sure that the spec says it should work this way?

Are you still experiencing this issue with the latest version of Firefox 5?

Comment 4

[Tim (fmdeveloper)]

Closing bug as Incomplete - if you are still experiencing this issue or have more information to provide feel free to post back here and we can re-open the bug. You can also get assistance by visiting the Firefox help site -> http://support.mozilla.com/en-US/kb/Ask+a+question