-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Early customizable select feature #2301
base: main
Are you sure you want to change the base?
Conversation
One obvious problem with creating this early feature is the lack of official spec. I think the most official artefact we have for this feature is the explainer on openui.org, which is what I've used for now, but which breaks the build. |
@@ -0,0 +1,11 @@ | |||
name: Customizable <select> | |||
description: The `<select>` element's appearance, including the button, selected option, picker dropdown, and options, can be customized using CSS. | |||
spec: https://open-ui.org/components/customizableselect/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link should be updated to https://open-ui.org/components/customizableselect/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't this the same link that's already there in the file?
Chromium I2S is out: https://groups.google.com/a/chromium.org/g/blink-dev/c/kN5LTzuTLVs/m/6HqTsmk3EQAJ |
@ddbeck I think we should merge this pretty much as is, allowing the OpenUI explainer URL. Customizable select has been in the works for many years, it needs to exist on our repo. We can use this as a guinea pig for early features if we want. |
Customizable select has been in discussions and in various states of prototypes for a few years already. It's feeling like the proposal is stabilizing now, and the feature has reached WHATWG stage 2 (soon stage 3). See this developer.chrome.com blog about it.
We've talked about how some (most?) features might need to get created early in the making, and I wanted to see what it felt like for this one.
@SachaG had asked for it in the past, in order to be able to link to it from State of HTML, where it's mentioned.