Re: [csswg-drafts] [css-ui] UA stylesheet for appearance:base `<select>` (#10857)

The CSS Working Group just discussed ``[css-ui] UA stylesheet for appearance:base `<select>` ``, and agreed to the following:

* `RESOLVED: adopt the UA stylesheet in the issue description for customizable select, with the exception of user-select which will be handled in a separate issue`

<details><summary>The full IRC log of that discussion</summary>
&lt;masonf> jarhar: anybody have any more feedback on the stylesheet? If not, can we resolve with what we have?<br>
&lt;masonf> scribenick: masonf<br>
&lt;masonf> smaug: I just commented somewhere about the styling for the option. I'm not sure how Chromium's current impl works, e.g. mousedown and drag.<br>
&lt;masonf> jarhar: good point, user-select none should get added to select to make that clear<br>
&lt;masonf> masonf: when you click drag let go?<br>
&lt;masonf> smaug: current impl doesn't do that now. No text selection happens.<br>
&lt;masonf> q?<br>
&lt;RRSAgent> logging to https://www.w3.org/2024/12/19-css-irc<br>
&lt;Zakim> RRSAgent, make logs Public<br>
&lt;RRSAgent> I have made the request, Zakim<br>
&lt;Zakim> Meeting: Cascading Style Sheets (CSS) Working Group Teleconference<br>
&lt;masonf> panos: do you wnat to file an issue that discusses user-select - study why it works the way it does<br>
&lt;masonf> jarhar: yeah, I'll see what we should do with user-select for &lt;select><br>
&lt;masonf> q?<br>
&lt;masonf> panos: any other feedback on the latest comment on the issue?<br>
&lt;masonf> jarhar: more specifically, the remaining UA stylesheet rules, which I've been keeping up to date.<br>
&lt;masonf> jarhar: since I'm hearing nothing, can we resolve to accept the rules?<br>
&lt;masonf> jarhar: if there's a user-select issue, we can tackle that as a separate issue.<br>
&lt;masonf> fantasai: we can handle interactivity as a separate issue. But the visual styling seems good, AFAICT<br>
&lt;masonf> panos: resolving to accept the styles as identified in Joey's latest comment.<br>
&lt;masonf> +1<br>
&lt;jarhar> proposed resolution: adopt the UA stylesheet in the issue description for customizable select<br>
&lt;masonf> +1<br>
&lt;jarhar> *with the exception of user-select which will be handled in a separate issue<br>
&lt;dbaron> +1<br>
&lt;dandclark> +1<br>
&lt;masonf> annevk: Tim isn't here, but I think he's been talking to Joey. But if there are issues, we can revisit.<br>
&lt;jarhar> RESOLVED: adopt the UA stylesheet in the issue description for customizable select, with the exception of user-select which will be handled in a separate issue<br>
&lt;masonf> panos: any other issues with UA stylesheet to discuss today?<br>
&lt;masonf> jarhar: nothing off the top of my head. I'm surprised we got a resolution, so we can move to the next issue. I'll also look through previous meetings. Happy for today.<br>
&lt;masonf> panos: before the next topic, any other folks have UA stylesheet comments?<br>
&lt;masonf> s/panos/past<br>
&lt;masonf> I bet that doesn't work<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10857#issuecomment-2554873900 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Thursday, 19 December 2024 16:15:26 UTC