- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Apr 2019 15:14:54 +0000
- To: public-css-archive@w3.org
It would be nice though if the CSSWG could be a little more precise in its resolutions. This issue has "initial value" in the subject, and the [OP](https://github.com/w3c/csswg-drafts/issues/3686#issue-415389501) clearly states that we implemented it as a _computed_ value. The description of [options](https://github.com/w3c/csswg-drafts/issues/3686#issuecomment-468098431) and the resolution: > RESOLVED: go with fantasai proposal (a) for initial value of counter increment? never mentions _used value_ once. Additionally, _initial value_ is a CSS term that implies a _computed value_. This creates confusion about what the CSSWG has discussed and resolved. Confusion that has on several occasions led us (Gecko) to implement things in the wrong way and thus waste precious resources on filing spec issues, re-implement it in the right way and update tests, filing bogus bug reports on other engines etc. For an UA vendor with limited resources like Mozilla this is VERY costly. I've also seen on several occasions that CSSWG members themselves don't agree afterwards what was being discussed and/or what the resolution means. I would suggest that you, before a resolution is made, take a minute to formulate a detailed and precise resolution statement that cannot be misinterpreted. In particular, when the word "value" appears in the resolution, make sure you **always** qualify every occurrence as a specified, computed, resolved or used value. Thanks. -- GitHub Notification of comment by MatsPalmgren Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3686#issuecomment-482612599 using your GitHub account
Received on Friday, 12 April 2019 15:14:55 UTC