- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Wed, 17 Apr 2013 15:18:08 -0700
- To: François REMY <francois.remy.dev@outlook.com>
- Cc: Alan Stearns <stearns@adobe.com>, "www-style@w3.org list" <www-style@w3.org>
On Wed, Apr 17, 2013 at 2:10 PM, François REMY <francois.remy.dev@outlook.com> wrote: >> One drawback to using a functional pseudo-element compared to an @rule is >> more typing. If you have more than one selector argument to pass to the >> function you have to repeat .container::distributed() for each selector. > > The lack of nested rules shouldn't be a reason to introduce more at-rules. Shouldn't selectors and @rules be kept orthogonal? > > BTW, I'm wondering why the spec is using a pseudo element instead of a new combinator like ".."? This has two drawbacks: firstly, consecutives pseudo-elements could become syntactically valid and "a::distributed(div)::before" does not make sense; secondly all the other pseudo-elements only match one element, not many. Plus, that's longer to type. This decision is recorded in previous discussions - using a combinator violates the implicit assumption that rtl selector evaluation always ends up with a subset of the elements matched by the first compound selector. ~TJ
Received on Wednesday, 17 April 2013 22:26:24 UTC