Steps to reproduce
- Open http://jsfiddle.net/cvrebert/Lxwc1eah/show/ in Edge or IE11.
- Open the JS console.
- Click the webpage’s checkbox so as to check it.
- Observe the JS console output.
Edge & IE11 incorrectly output:
click event should fire before the
change event (as opposed to the other way around).
In the example, after following the steps, the console should read:
Dev Channel specific:
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Mara P.”
Changed Assigned To to “Sermet I.”
Changed Assigned To to “Bogdan B.”
Changed Assigned To from “Bogdan B.” to “Jonathan H.”
Changed Status to “Confirmed”
Per the HTML spec, clicking on an `` should cause a
clickevent to be fired and then subsequently a
changeevent to be fired. However, Edge fires these events in the wrong order; it fires
changeand then fires
Relevant portions of the spec:
When a user agent is to [[[run authentic click activation steps]]] for a given event event, it must follow these steps:
6. Dispatch event (the required
clickevent) at target.
If there is an element e and the
clickevent is not canceled, [[[run post-click activation steps]]] on element e.
When a user agent is to [[[run post-click activation steps]]] on an element, it must run the [[[activation behaviour]]] defined for that element, if any.
18.104.22.168.16 Checkbox state (type=checkbox)
The [[[activation behaviour]]] is to fire a simple event that bubbles named
inputat the element and then fire a simple event that bubbles named
changeat the element.
Added a new test case page since the original is 404’ing.
Note that the issue affects checkboxes AND radio buttons, and is a carry over bug from Internet Explorer (this is not new to Edge)
Seems the issue tracker’s Markdown is broken. The original link should be: