Joey Arhar
Joey Arhar
I think that multi select will have a button and a popup, in which case we won't have to do anything differently with the button.
> Can we change the "" entry to "Customizable " for this year? That is the new name for it: https://open-ui.org/components/customizableselect (maybe we keep in parentheses?) I think this meant...
> So just so I'm clear, this went from ``, to ``, to now just `` but with this CSS snippet required? > > ``` > select, > ::picker(select) {...
If the custom element is upgraded and has a setter for the property, then when react renders it should assign the boolean you're providing in the JSX into the custom...
Thanks for opening this! We could just make arrow right act the same as arrow down and make arrow left act the same as arrow up by default in order...
The HTML spec currently says that for customizable select, there is UA defined behavior with keys which may focus another option: https://html.spec.whatwg.org/multipage/form-elements.html#focus-another-option This means that we are free to implement...
One more thing I forgot to clarify - if you put a `` inside a ``, then the association will be set up automatically without the need for the `for`...
I created an explainer PR for this here: https://github.com/openui/open-ui/pull/1071
Sounds like the same issue as this? https://issues.chromium.org/issues/40281699
Thanks Scott! I wonder how menus which are mostly actions but also have a few links fit into this. For example, in the google docs menubar there is a link...