W3C home > Mailing lists > Public > public-css-archive@w3.org > August 2019

[csswg-drafts] [css-lists-3] Compute non-existent `list-style-type` <counter-style> to `decimal`? (#4210)

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Sat, 17 Aug 2019 01:07:11 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-481831473-1566004030-sysbot+gh@w3.org>
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-lists-3] Compute non-existent `list-style-type` <counter-style> to `decimal`? ==
In https://lists.w3.org/Archives/Public/www-style/2016May/0076.html @upsuper wrote:
> Recently, there is a behavior change in Gecko which makes list-style-type be computed to 'decimal' when the specified counter style doesn't exist, rather than keeping the specified nonexistent one. This change helps us save a string for common cases, and simplify some
code. None of which is a big deal, though.
>
> I'm not completely sure what does the spec say for this case. It seems to me the old behavior is more conformant, but I guess the new behavior might be perferable, since it makes the computed value match the used value. So I propose changing the spec to this behavior.
>
> What do you think?

@tabatkins replied
> I'm fine with this if others are; I don't see any particular reason to keep the non-existent type in computed style.  Whichever way is more convenient for implementations is ok with me.

Any other opinions, or should we update the spec to match Gecko?

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4210 using your GitHub account
Received on Saturday, 17 August 2019 01:07:14 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:31:13 UTC