- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 Sep 2024 16:02:41 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-ui] UA stylesheet for appearance:base `<select>` ``, and agreed to the following: * `RESOLVED: font properties won't be set in the UA style sheet` <details><summary>The full IRC log of that discussion</summary> <chrishtr> jarhar: there has been good discussion in the issue, and I've created two sub-issues for some topics<br> <chrishtr> jarhar: don't know if there is anything specific to resolve in the issue right now?<br> <chrishtr> fantasai: we could resolve to inherit the font?<br> <dbaron> yeah, +1 to inheriting the font<br> <chrishtr> ntim: think it could be good to delay this discussion to after or during TPAC<br> <chrishtr> fantasai: agree in general<br> <chrishtr> q+<br> <chrishtr> fantasai: also for all form controls and not just select<br> <astearns> ack fantasai<br> <chrishtr> jensimmons: would be best to discuss then/later<br> <chrishtr> jarhar: I'd like to discuss things like which pseudo elements we should add, how to specify colors, ...<br> <chrishtr> fantasai: let's reschedule so that the breakout is first?<br> <chrishtr> astearns: we could have tentative discussions at the breakout and then finalize them at the group later<br> <fantasai> s/breakout is first/breakout agenda is rescheduled into the OpenUI joint meeting/<br> <sanketj_> https://github.com/whatwg/meta/issues/326<br> <keithamus> scribe+<br> <keithamus> chrishtr: while we do want consistent styles, `<select>` is being worked on this year and we need to ensure we don't unreasonably delay decisions based on that.<br> <keithamus> chrishtr: we can use it as a place to set precedent for the others<br> <keithamus> astearns: So here is the precedent, but if we make a mistake we can change them as we integrate into the larger set?<br> <keithamus> chrishtr: sure we can make changes later.<br> <ntim> (can't talk right now) I'm hoping that TPAC gives enough time to resolve most things regarding UA stylesheets! My goal is more to help drive select's direction not block its progress :)<br> <jarhar> +1 to using unset for font properties<br> <ntim> (or not setting the font at all)<br> <chrishtr> RESOLVED: font properties won't be set in the UA style sheet<br> <chrishtr> jarhar: this issue was created because accessibility experts are concerned about authors ending up with inaccessibile structures<br> <fantasai> i/jarhar:/Topic: Content Model/<br> <fantasai> github: https://github.com/whatwg/html/issues/10317<br> <chrishtr> jarhar: we should discuss which are allowed so as to preserve accessibility. I worked with accessibility experts from OpenUI and came up with a list of elements which should be allowed within select: divs, spans, img, text within options but outside<br> <RRSAgent> I have made the request to generate https://www.w3.org/2024/09/19-css-minutes.html fantasai<br> <chrishtr> jarhar: and legend elements as child of optgroup to replace label<br> <chrishtr> jarhar: this has the same a11y mapping but is more styleable<br> <jarhar> q?<br> <astearns> ack chrishtr<br> <emilio> q+<br> <chrishtr> jarhar: my HTML spec PR is ready to go so from my perspective it's ready. should we go with this approach?<br> <astearns> ack emilio<br> <chrishtr> emilio: curious if we're going to have special rendering for legend like we have for fieldset, or are there any other special rendering rules?<br> <astearns> pr: https://github.com/whatwg/html/pull/10586<br> <chrishtr> emilio: if you put a legend into a fieldset the the rendering is quite special. the first thing gets moved up to the top regardless of where it is in the DOM, and other layout tree reparenting.<br> <chrishtr> emilio: hoping we don't have to do any of that<br> <astearns> q+<br> <chrishtr> jarhar: my preference is also not to do anything special. didn't come across any need to have special rendering in prototyping in Chromium. I just set up the a11y mappings and changed the rendering of the optgroup element so it would stop rendering the label attribute part when there is a legend child<br> <chrishtr> fantasai: on the PR: it says div and span, but not various other elements like em or bdo. why not?<br> <chrishtr> jensimmons: there are so many other elements that seem reasonable?<br> <chrishtr> fantasai: ruby also<br> <chrishtr> jarhar: these are good points and should be included within option elements. these rules are about content outside option elements.<br> <astearns> ack fantasai<br> <chrishtr> jarhar: maybe we can use a more broad rule for inside-option parts<br> <chrishtr> fantasai: span or other inline elements don't belong outside option<br> <chrishtr> fantasai: div allowed but not span because span is inline<br> <chrishtr> astearns: are there tests?<br> <chrishtr> jarhar: the tests for the content model: not sure how to do that. in the Chromium implementation, we render everything but use developer tooling to guide people towards accessible outcomes. tl;dr I don't know how to test it in WPT.<br> <astearns> ack astearns<br> <astearns> zakim, end meeting<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-2361423540 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 September 2024 16:02:42 UTC