- From: Joey Arhar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Aug 2024 23:16:19 +0000
- To: public-css-archive@w3.org
Thanks for the discussion everyone! I’d like to build a resolution based on fantasai’s comments at the end of the meeting: > fantasai: …In terms of select specifically, it's special, google's been working hard on it but it's also a form control where the picker and all components can be > represented as elements in the page. > ... most other form controls have pickers with UA magic > ... it might be reasonable to ship appearance:base-select just for selects, while we work on the rest, then ship appearance:base for everything I’d like to propose the following resolution: - `appearance:base-select` opts-in both the in-page control and the picker for `<select>`. - `::picker { appearance: base }` will be used for all form control elements (including `<select>`) as an opt-in/incremental shipping plan, per Apple’s proposal - `appearance:base` will apply to the in-page parts of all form controls (including `<select>`) -- GitHub Notification of comment by josepharhar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10440#issuecomment-2276868161 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 8 August 2024 23:16:20 UTC