Joey Arhar

> Maybe injecting the disclosure-open counter style would work? I am implementing this in the prototype here: https://chromium-review.googlesource.com/c/chromium/src/+/5660759 I'm having a hard time getting `select::select-fallback-button::after` to work in author stylesheets,...

> Maybe injecting the disclosure-open counter style would work? @fantasai does this seem like what you were thinking of? ``` select::select-fallback-button::after { padding-inline-start: 0.5em; } select:open::select-fallback-button::after { content: counter(foo, disclosure-open);...

> > Maybe injecting the disclosure-open counter style would work? > > @fantasai does this seem like what you were thinking of? > > ``` > select::select-fallback-button::after { > padding-inline-start:...

The pseudo-elements and UA styles mentioned in my last two comments were futher refined and resolved in further discussions in the sub-issues here, so I'm going to close this: https://github.com/whatwg/html/issues/9799

> Just curious - is there a reason this was split from https://github.com/w3c/csswg-drafts/issues/9284? If it was just to reset the conversation given a more stable design from HTML/OpenUI, should we...

> How often is cloning done when an option (that's also the selected option) is being mutated? I.e., what is the timing story. Right now my prototype does it synchronously...

> Thanks! Right, microtask timing might be preferable to avoid cloning too often. As for your last point, `` is inserted before any of `` elements, so that does not...

I don't see how this proposal limits what we can do for select multiple. I think that for now, `` shouldn't do anything when the select has the multiple attribute.

Does figuring out how to represent multiple options in `` for `` address your concern?

I filed a separate issue to discuss timing here: https://github.com/whatwg/html/issues/10520 I filed it in whatwg because it doesn't seem to have much to do with CSS or the general API...