Joey Arhar

Agreed! I'll omit the properties which have their default.

This PR won't be merged and will instead be included in a bigger PR including all customizable select PRs: https://github.com/whatwg/html/pull/10548

I'm on it, thanks for finding this! And sorry for accidentally adding the duplicate, I can clearly see that I didn't even use it in the patch I added.

https://chromium-review.googlesource.com/c/chromium/src/+/5947328

Looks like my patch passes all tests in chromium, it should be merged soon and then automatically upstreamed here.

Proposed agenda: 1. Update on specs: https://github.com/whatwg/html/issues/9799#issue-1914386972 - Requesting stage 3 again, once selectedoption cloning issue is resolved 3. https://github.com/w3c/csswg-drafts/issues/10908 4. https://github.com/w3c/csswg-drafts/issues/10909 5. https://github.com/w3c/csswg-drafts/issues/10857 6. https://github.com/openui/open-ui/issues/1087 7. https://github.com/w3c/csswg-drafts/issues/11039

next meeting: https://github.com/whatwg/html/issues/10730

Using ::marker was also mentioned, but I imagine it would make things harder since it has logic tied to list item rendernig that I imagine could be hard to work...

Some things I'd like to resolve on, in this order: 1. Should we create new pseudo-elements for the dropdown icon and checkmark? Presumably we would have one for the checkmark...

From an implementation point of view, I would prefer to make these like ::before and ::after because I want the content property to work on them, and if it has...