W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2020

[csswg-drafts] [css-cascade][Editorial] Why list the global values for `all`? (#5740)

From: Lea Verou via GitHub <sysbot+gh@w3.org>
Date: Mon, 23 Nov 2020 17:06:23 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-748975748-1606151182-sysbot+gh@w3.org>
LeaVerou has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-cascade][Editorial] Why list the global values for `all`? ==

> Value: initial | inherit | unset | revert

These keywords are valid in every other CSS property, yet we don’t list them explicitly. Why should `all` be an exception? This means that if we add another global keyword, we need to remember to add it here too, and old versions of the spec will be out of sync.

I'd propose changing it to: 

> Value: (Only global values)


> Value: (nothing)

and explain in the prose.

Also, we should avoid using "global keywords" in the value, as we may introduce some kind of global value that is not a keyword in the future.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5740 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 November 2020 17:06:25 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:22 UTC