Skip to content

Remove all:unset from select button#12371

Open
josepharhar wants to merge 1 commit intowhatwg:mainfrom
josepharhar:buttonunset
Open

Remove all:unset from select button#12371
josepharhar wants to merge 1 commit intowhatwg:mainfrom
josepharhar:buttonunset

Conversation

@josepharhar
Copy link
Copy Markdown
Contributor

@josepharhar josepharhar commented Apr 14, 2026

all:unset is not very performant and was just a convenient way to remove appearance:auto UA styles. We can use appearance:base instead, which should achieve the same goal without reseting every property.

Fixes #12121

  • At least two implementers are interested (and none opposed):
    • Chromium
  • Tests are written and can be reviewed and commented upon at:
    • TODO
  • Implementation bugs are filed:
    • Chromium: …
    • 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.)


/rendering.html ( diff )

Copy link
Copy Markdown
Member

@keithamus keithamus left a comment

Choose a reason for hiding this comment

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

LGTM 😄

@annevk
Copy link
Copy Markdown
Member

annevk commented Apr 15, 2026

It seems like the discussion in the issue hasn't concluded yet.

@annevk annevk added the do not merge yet Pull request must not be merged per rationale in comment label Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge yet Pull request must not be merged per rationale in comment

Development

Successfully merging this pull request may close these issues.

Should appearance: base select button have both all: unset and display: contents ?

3 participants