<select> element fires the onchange event when no change has occurred

Fixed Issue #6495332


Feb 9, 2016
This issue is public.
Reported by 0 people

Sign in to watch or report this issue.

Steps to reproduce


Repro Steps:

See attachment, but essentially this code in an HTML page will trigger it.

Note: more details to come… it turns out there’s more complication to this…

<select name="foo" onchange="this.form.submit();">
<option value=""></option>

1.) If the JS code attempts to set a value that isn’t in the list of valid values… what is the expected behavior?
a.) It’s a no-op, silently swallow?
b.) Throw an error of some kind?
c.) Allow this to be set, even though it is not a valid option in the list?

2.) If the answer to #1 above is anything but "c", is it fair to say that the “selection” remains as the select was when it loaded, and thus opening it should NOT trigger an onchange event?

Expected Results:

The onchange event should only fire if an actual change has occurred. This broken behavior is causing (redundant) expensive query reloads on pages in our web application due to a form submission tied to the change event.

Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Sermet I.”

      Changed Assigned To to “Bogdan B.”

      Changed Status to “Won’t fix”

      Changed Status from “Won’t fix” to “Fixed”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 16299 and is available in our current public build.

      Best Wishes,
      The MS Edge Team

    You need to sign in to your Microsoft account to add a comment.

    Sign in