Chrome 134 supports customizable <select> element#26171
Merged
Conversation
10 tasks
Contributor
Author
|
This is still failing. Do I need to wait for BCD to slurp up a new package version before the |
<select> element
caugner
approved these changes
Mar 11, 2025
Merged
This was referenced Mar 14, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Chrome 134 supports customizable
<select>elements (see https://chromestatus.com/feature/5737365999976448).This includes a multitude of sub-features; this PR adds data for the new ones we haven't already got data for, which are as follows:
<selectedcontent>element::picker()pseudo-element::picker-iconpseudo-element::checkmarkpseudo-elementappearancepropertybase-selectvalue (which is currently specified asbase, but I think this might change soon).I'm setting this as a draft for now because BCD doesn't recognize the CSS Form Control Styling Level 1 as a valid spec. I've filed an issue to ask if I can get it added to- UPDATE, this issue got fixed.browser-specs: see w3c/browser-specs#1723Test results and supporting details
Related issues
MDN content: mdn/content#38470