- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Jun 2021 23:11:09 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-counter-style] overriding symbolic counter styles.`, and agreed to the following: * `RESOLVED: When you extend a predefined symbolic you are extending the version defined in the spec` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-counter-style] overriding symbolic counter styles.<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/3584<br> <dael> TabAtkins: IN current spec I went conserivitive with locking down styles so could not be overwritten.<br> <dael> TabAtkins: After prodding I added a few things in addition to decimal. Disc. Emilio is asking for others not to be overwritable. rendered specially by browsers so requires a bit more work.<br> <dael> TabAtkins: I'm happy with this. You can make your own and give it your own name. Need sign off<br> <dael> astearns: Yes, there is the out of making your own. Do you think there is a compat problem where we will remove people's overrides?<br> <dael> TabAtkins: I strongly doubt. If you're doing a counter style named square that is not squares you're bringing it on yourself<br> <dael> astearns: Your special squares is the thing. Going back to normal boring squares is not that terrible<br> <dael> astearns: Any concerns with the change?<br> <dael> astearns: Prop: Make app predefined symbolic counter styles not overwritable<br> <dael> TabAtkins: All predefined symbolics<br> <dael> s/app/all<br> <dael> astearns: Obj?<br> <dael> Resolved: Make all predefined symbolic counter styles not overwritable<br> <dael> TabAtkins: What if you extend these?<br> <dael> TabAtkins: Two major options<br> <dael> TabAtkins: First is that whenever you extend a predefined counter style the thing you are extending is the spec version, not what browsers do. Means you might get slightly different glyph<br> <dael> TabAtkins: Still approx the same<br> <dael> TabAtkins: Other is doing more subtle thing where certain descriptors cause revert to version in spec. That still has complicaitons<br> <dael> TabAtkins: Prop: if you extend a predefined symbolic you are extending the version defined in spec not as rendered in browsers<br> <dael> fantasai: Not sure on this one<br> <dael> fantasai: Reasonable you might want to extend with some such as speak-as without effecting rendering<br> <dael> TabAtkins: Symbolics with speak-as best you can do it make them read decimal of counter. Doing that one something that doesn't render a number doesn't sound good<br> <dael> TabAtkins: Decimal is fine. Predefined symbolics where in spec you can render in other ways<br> <dael> fantasai: So this is just circle, disc type ones?<br> <dael> TabAtkins: Yeah<br> <dael> oriol: This is how FF and Chromium render so it is fine<br> <dael> astearns: Prop: When you extend a predefined symbolic you are extending the version defined in the spec<br> <dael> astearns: Obj?<br> <dael> RESOLVED: When you extend a predefined symbolic you are extending the version defined in the spec<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3584#issuecomment-853440806 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 June 2021 23:11:43 UTC