- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Sep 2019 23:53:38 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``Compute non-existent `list-style-type` <counter-style> to `decimal`?``, and agreed to the following: * `RESOLVED: No change re computed value of list-style-type` <details><summary>The full IRC log of that discussion</summary> <AmeliaBR> Topic: Compute non-existent `list-style-type` <counter-style> to `decimal`?<br> <AmeliaBR> github: https://github.com/w3c/csswg-drafts/issues/4210<br> <AmeliaBR> TabAtkins: fantasai discovered this when cleaning up lists spec. Issue is what should computed style be if you set the list-style-type to a custom ident that doesn't currently exist.<br> <AmeliaBR> …The used style is decimal. But computing that eagerly (as Firefox used to do) can be problematic, since @-rule could be added later.<br> <AmeliaBR> …I don't think any other browsers yet implement custom idents; they reject at parse time. I think best to follow current Firefox. Computed value is the custom ident.<br> <fantasai> s/cleaning up/doing archaeology for the/<br> <AmeliaBR> astearns: There are Firefox folks in thread pointing out that current behavior wasn't really intentional.<br> <AmeliaBR> TabAtkins: That's OK. It's still good behavior. Let's spec it properly.<br> <AmeliaBR> dbaron: If Emilio's OK with it, I'm OK with it.<br> <AmeliaBR> TabAtkins: He wrote the current Firefox behavior, so I hope so.<br> <AmeliaBR> astearns: And this will just be no-change to current spec.<br> <AmeliaBR> RESOLVED: No change re computed value of list-style-type<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4210#issuecomment-528137325 using your GitHub account
Received on Wednesday, 4 September 2019 23:53:39 UTC