Skip to content

Conversation

@josepharhar
Copy link
Contributor

@josepharhar josepharhar commented Jan 13, 2026

In order to make the selectedness setting algorithm match implementations, this PR makes the selectedness setting algorithm avoid changing the selectedness of option elements which haven't ran their insertion steps yet by checking whether the options have their cached nearest ancestor select element assigned yet or not.

This was discussed here: #11825

  • At least two implementers are interested (and none opposed):
    • Chromium
  • Tests are written and can be reviewed and commented upon at:
    • I need to look into it, but I suspect that this is already covered by existing tests
  • Implementation bugs are filed:
    • Chromium: Already implemented
    • Gecko: …
    • WebKit: …
  • Corresponding HTML AAM & ARIA in HTML issues & PRs: Not needed
  • MDN issue is filed: Not needed
  • The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)


/form-elements.html ( diff )

In order to make the selectedness setting algorithm match
implementations, this PR makes the selectedness setting algorithm avoid
changing the selectedness of option elements which haven't ran their
insertion steps yet by checking whether the options have their cached
nearest ancestor select element assigned yet or not.

This was discussed here: whatwg#11825
Copy link
Member

@annevk annevk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How does this PR relate to #11890? It's getting quite confusing.

@josepharhar
Copy link
Contributor Author

How does this PR relate to #11890? It's getting quite confusing.

I listed some different ways we can proceed here: #11890 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants