Programmatic changes to selected options in select[multiple] do not render immediately

Confirmed Issue #9628212 • Assigned to Bogdan B.


Gary B.
Nov 2, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

See the following plunker in Edge.

Click the “Toggle Selecting All Elements” button, you may immediately notice that the last option does not select - until you hover over it. Click the button again and you will likely see that nothing changes in the select box until you hover over it.


Comments and activity

  • Just in case the plunker goes away, here is the code.

        select[multiple] issues
          New York
          San Fransisco
        Toggle Selecting All Elements
  • Ok, that didn’t quite work. I’ve added an attachment instead.

  • Microsoft Edge Team

    Changed Assigned To to “Ibrahim O.”

    Changed Assigned To to “Rick J.”

    Changed Assigned To to “Bogdan B.”

    Changed Assigned To from “Bogdan B.” to “Kurt C.”

    Changed Status to “Confirmed”

  • I believe my app is suffering from this problem. I have a real use-case which reproduces this issue in a single-page-app. Example:

    That page should have multiple select inputs below each .

    However, the select elements are rendered and manipulated with client-side code and the ‘delay’ caused by this bug produces errors. For example, during manipulation I have noticed that:
    – is zero.
    – is 15.
    Clearly those lengths should be equal but they’re reportedly different.

  • Microsoft Edge Team

    Changed Assigned To from “Kurt C.” to “Jonathan H.”

    Changed Assigned To from “Jonathan H.” to “Bogdan B.”

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

Sign in