Home Dashboard Directory Help
Search

dispatchEvent doesn't trigger click when called from on click by M. Laponder


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


Type: Bug
ID: 785769
Opened: 4/29/2013 1:50:14 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description


In our application we register each event and check if all condition are met to execute the code. If all conditions are met we dispatch the event with dispatchEvent to really execute the code. In some situations this is done immediately, in some situation this is done later (e.g., when an xmlhttp request returns), or not at all (e.g., when an xmlhttp request returns with an error code). When it is done immediately this fails in IE10 while it succeeds in other browser (Chrome, FF,Safari).

Details
Sign in to post a comment.
Posted by M. Laponder on 5/5/2013 at 11:19 PM
Is my comment being evaluated ? The bug has been marked as not reproducible, but if you read my report and comment thoroughly you can see you did reproduce it. Please reactivate the bug, I will open a new report shortly if it is not reactivated.
Posted by M. Laponder on 4/30/2013 at 11:40 PM
Please read the expected results parts which is specified in the bug, the expected results are:

Event dispatched: undefined , type: click
Event NOT received by dispatch
Now dispatching the event
Event dispatched: true , type: click
Event received by dispatch

Note the last two lines. These last two lines don't appear when running the test in IE10. It is not the same behavior as FF,Chrome and Safari. Please re-evaluate the bug.

I can't see any option to reactivate the bug, so I will monitor this one for now after adding this comment.
Posted by Microsoft on 4/29/2013 at 11:24 AM
Thank you for your feedback.

We are currently unable to reproduce this issue as described.

The console shows :
Event dispatched: undefined , type: click
Event NOT received by dispatch
Now dispatching the event

and if there is a double click, the dialog box shows: by dispatch
which is the same behavior on FF, Chrome and Safari.

We value your feedback. If you have additional information that can help us recreate this issue — such as a specific url, more detailed steps, test results from different machines, or additional conditions — please reactivate the bug or submit a new bug with more details on how to reproduce the issue. You can also read the guidelines at https://connect.microsoft.com/IE/content/content.aspx?ContentID=16254 regarding filing a good bug report.

Best regards,

The Internet Explorer Team
Sign in to post a workaround.