W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2017

[csswg-drafts] [custom-selectors] Why it’s @custom-selector and not @selector?

From: Valtteri Laitinen via GitHub <sysbot+gh@w3.org>
Date: Mon, 04 Dec 2017 18:07:14 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-279092862-1512410833-sysbot+gh@w3.org>
valtlai has just created a new issue for https://github.com/w3c/csswg-drafts:

== [custom-selectors] Why it’s @custom-selector and not @selector? ==
I think `@custom-selector` feels a bit verbose. Why it isn’t called `@selector`?

https://drafts.csswg.org/css-extensions/#custom-selectors

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2039 using your GitHub account
Received on Monday, 4 December 2017 18:07:18 UTC

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