- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Sep 2019 22:35:46 +0000
- To: public-css-archive@w3.org
I don't see why we should go with unspecified, if we can settle on an answer. That's only really something we do if we have multiple incompatible impls and no good way to find consensus between them. As I said before, I don't think there's any particularly good reason to choose one way or the other, so we should do whatever is easiest. Looks like leaving the style around in computed style works best, as it lets Firefox delay having to resolve that style until later in the pipeline. I imagine Blink would benefit similarly (tho right now we don't implement @counter-style at all, so it's just an invalid declaration right now). -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4210#issuecomment-528119090 using your GitHub account
Received on Wednesday, 4 September 2019 22:35:48 UTC