Early customizable select feature#2301
Conversation
github-actions
bot
added
the
feature definition
|
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.
This link should be updated to https://open-ui.org/components/customizableselect/
There was a problem hiding this comment.
Isn't this the same link that's already there in the file?
ddbeck
added
the
early features
|
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. |
github-actions
bot
added
the
tools and infrastructure
ddbeck
left a comment
ddbeck
left a comment
There was a problem hiding this comment.
I'm happy with this, but before merging, I'd like the spec link exception to point at something that'll tell us when the specification story is resolved.
scripts/specs.ts
Outdated
| ], | ||
| [ | ||
| "https://open-ui.org/components/customizableselect/", | ||
| "Allowed because customizable select doesn't yet have a spec URL. And even when it does, it will be defined in multiple HTML, CSS, and ARIA specs. The OpenUI explainer is the only central place that defines the component at the moment." |
There was a problem hiding this comment.
Is there a good issue or PR to link to that would prompt us to remove this exception? Basically, I want to know where to look when we have "real" spec links to replace this with.
Something like this?
| "Allowed because customizable select doesn't yet have a spec URL. And even when it does, it will be defined in multiple HTML, CSS, and ARIA specs. The OpenUI explainer is the only central place that defines the component at the moment." | |
| "Allowed because customizable select doesn't yet have a spec URL. And even when it does, it will be defined in multiple HTML, CSS, and ARIA specs. The OpenUI explainer is the only central place that defines the component at the moment. Remove when SOMEURL merges." |
There was a problem hiding this comment.
There are multiple PRs, not just one. See my previous comment: #2301 (comment)
Out of those, I'm guessing it would be enough to link to the following ones:
whatwg/html#10586
whatwg/html#10629
whatwg/html#10633
@josepharhar are you able to help select one (or more, but ideally a small number) spec PR that would basically signify "that's it, customizable select is now in the spec"?
There was a problem hiding this comment.
Sorry for being slow - if I had to choose one of the PRs, I'd choose the base appearance rendering PR as the best indicator for the spec of customizable select: whatwg/html#10629
There was a problem hiding this comment.
I've added them all in the meantime 😆
Thank you.
Superseded by web-platform-dx#2301
* Remove selectlist feature Superseded by #2301 * Remove scroll-marker draft This looks premature, particularly without a process for early features.
This was added to web-platform-dx here: web-platform-dx/web-features#2301 Change-Id: I289fa06eb3aca261b09ba7c51f5de8257a9984dc Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6551553 Reviewed-by: Mason Freed <masonf@chromium.org> Commit-Queue: Joey Arhar <jarhar@chromium.org> Cr-Commit-Position: refs/heads/main@{#1462179}
3 participants
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.