- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Jun 2023 17:02:51 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-counter-styles-3] Should "Ready-made Counter Styles" be supported by UA?`, and agreed to the following: * `RESOLVED: Work with i18nWG to republishe Ready-Made Counter Styles as a W3C Registry allowing CSSWG and/or i18nWG to update; update Counter Styles to require everything in the Registry` <details><summary>The full IRC log of that discussion</summary> <fantasai> ??: When we were implementing counter styles on webkit side, I saw this list maintained for Ready-made Counter Styles for different languages<br> <fantasai> ... but this was not intended to be supported by browsers<br> <fantasai> ... so I wanted to understand why<br> <fantasai> jensimmons: Proposal is to take this stylesheet and put it into the UA stylesheet for browsers<br> <fantasai> ... so that all these styles are supported by browsers out of the box<br> <emilio> q+<br> <fantasai> ... for all the languages equally, so devs don't have to copy-paste<br> <fantasai> TabAtkins: I have no objections to in or out<br> <dbaron> s/??/vitorroriz/<br> <fantasai> ... we agreed to move out at the time partially because we didn't want to show favoritism that we happened to have listed<br> <fantasai> ... so restricted to list in CSS2<br> <fantasai> ... but list has been enhanced substantially by i18nWG over last 8 years<br> <fantasai> ... so as long as implementers are fine with it, I'm OK too<br> <emilio> FWIW I think Gecko ships at least an early version of this? https://searchfox.org/mozilla-central/rev/fb55a4ee44a9a95d099aa806ca494eb988252ded/layout/style/res/counterstyles.css<br> <fantasai> ... dbaron did point out that some of these changes could have web-compat impacts<br> <fantasai> ... I reviewed the changes, given intended use cases and the practical use cases ppl use these for<br> <fantasai> ... I suspect web-compat for such changes are going to be minimal<br> <fantasai> ... I think this is going to be low chance of compat<br> <Rossen_> q?<br> <fantasai> ... and if author disagrees with what we do, they can override; spec allows this<br> <fantasai> ... just need to make sure that whatever we do, it's still easily editable by i18nwg<br> <fantasai> ... There was some discussion about putting UA styles in HTML stylesheet, but that would create a lot of friction for updates, so don't recommend<br> <fantasai> jensimmons: I think one issue that will come up, e.g. making content for WWDC, one of the examples I used made upper-serbo-croatian<br> <dbaron> I'd note that the UA styles here are for all document languages rather than just for HTML, and I *think* such UA styles don't go in the HTML spec...<br> <fantasai> ... term was used in the past, but in this day and age, would be better to use a different term...<br> <fantasai> ... but there's going to be some touchy political issues around naming these things<br> <fantasai> ... if in CSS, then we'd have to add aliases or something<br> <fantasai> ... so some homework for CSSWG over the years<br> <tantek> +1 jensimmons I saw chatter about that example as well<br> <fantasai> ... but feels important to do, to include all languages of the world not just those in CSS2<br> <TabAtkins> yeah, so long as we don't drop anything, just add aliases, it should always be fine<br> <fantasai> emilio: for the case Jen mentioned, keep old name around and add new if needed<br> <fantasai> emilio: ant to point out, Gecko ships an early version of this<br> <fantasai> s/ant/want/<br> <fantasai> emilio: I tend to think that we should really support this in the browser, don't care where they live<br> <Rossen_> ack fantasai<br> <Zakim> fantasai, you wanted to comment on process<br> <Rossen_> ack emilio<br> <TabAtkins> fantasai: I don't think the right thing is to fold into Counter Styles 3, that's focused on the mechanism of counter styles and we want this to go to Rec<br> <TabAtkins> fantasai: But this could be a document, maybe a Registry which is new and allows easy updates, and commision CSSWG and i18nWG to add new things to it, make it a joint publications<br> <bkardell_> registry is interesting<br> <florian> [that makes sense to me]<br> <TabAtkins> fantasai: And counter styles can require including everything in the registry<br> <fantasai> jensimmons: Benefit is better compat<br> <TabAtkins> fantasai: Just putting them in the same doc makes things harder to update<br> <fantasai> jensimmons: We don't really have interop between browsers for this<br> <fantasai> jensimmons: expecting that browsers will regularly ship all of them will help authors in that way<br> <fantasai> TabAtkins: I propose we take fantasai's idea, take into registry jointly published by CSSWG and i18nWG<br> <fantasai> TabAtkins: and have Counter Styles require everything in the registry<br> <fantasai> Rossen_: Any objections to that?<br> <gtalbot> [crickets stridulation noises]<br> <fantasai> RESOLVED: Work with i18nWG to republishe Ready-Made Counter Styles as a W3C Registry allowing CSSWG and/or i18nWG to update; update Counter Styles to require everything in the Registry<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8636#issuecomment-1591665495 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 June 2023 17:02:53 UTC