W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2018

[csswg-drafts] [css-lists][cssom] Should the serialization of counter-reset/increment include default values?

From: Gerald Squelart via GitHub <sysbot+gh@w3.org>
Date: Tue, 01 May 2018 04:34:40 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-319113647-1525149279-sysbot+gh@w3.org>
squelart has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-lists][cssom] Should the serialization of counter-reset/increment include default values? ==
In the CSSOM general principles of serialization: https://drafts.csswg.org/cssom/#serializing-css-values
> If component values can be omitted or replaced with a shorter representation without changing the meaning of the value, omit/replace them.

This would suggest that if a counter-reset or counter-increment was declared with no values, its serialization should *not* include the default value (resp. 0 or 1).

E.g.: `<body style="counter-increment: abc" onload="alert(document.body.style.counterIncrement)">` should display "abc".
Edge 42 does this.
However Firefox 60, Chrome 66, and Safari 11.1 currently display "abc 1".

So, should the general rule be followed, or should there be a special case for counters? (Or something else?)

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2635 using your GitHub account
Received on Tuesday, 1 May 2018 04:35:06 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:29 UTC