Re: [csswg-drafts] [css-ui] How do `appearance: none` and `appearance: auto` render the rich `<select>` markup? (#10332)

> appearance:none and appearance:auto both use the same native or platform-specific picker, so I don’t see how we can make appearance:none switch to using an unrestricted non-native picker without breaking websites which expect to get a native picker. On at least Chromium browsers, this picker exists within a separate OS window that can extend beyond the content area, meaning it cannot contain arbitrary content without creating security issues.

I'm curious what is the impact of making explicit `appearance: none` (e.g. not `appearance: auto` that falls back to a certain appearance because some properties were set) switch to the same picker that is used by `appearance: base`, `select` has `appearance: auto` by default in UA stylesheets, so I suspect this might be feasible with little compat impact. I suspect very few sites use `appearance: none` explicitly on the select element.


-- 
GitHub Notification of comment by nt1m
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10332#issuecomment-2111789308 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 15 May 2024 07:34:16 UTC