W3C home > Mailing lists > Public > www-style@w3.org > June 2017

Re: [selectors4] multiple pseudo-elements per selector

From: fantasai <fantasai.lists@inkedblade.net>
Date: Wed, 21 Jun 2017 14:17:16 -0400
To: Bruce Lawson <bruce@brucelawson.co.uk>
Cc: www-style@w3.org
Message-ID: <72ee8638-839a-e234-5072-1bdcc9755c74@inkedblade.net>
On 06/21/2017 01:57 PM, Bruce Lawson wrote:
> Thanks fantasai
> so the reasons that multiple pseudo-elements isn't allowed is primarily 
> implementation complexity and (I assume) performance implications of
> that complexity, rather than any philosophical objections?

Primarily complexity, rather than performance. But even if a particular
combination was relatively simple, we don't want to add features that
don't have strong use cases since even simple features require work
(spec, implementation, testing). The key thing to remember here is that
each combination would likely require its own code: only the parsing
bit could be handled generically, and that's a very minor fraction of
the work involved in handling a pseudo-element.

> Do any examples of specific combinations that are potentially allowable spring to mind?

I remember there being use cases for some specific combinations,
but I can't remember what they were atm. ^_^;;

::marker::first-line definitely seems unlikely, though. =)

Received on Wednesday, 21 June 2017 18:17:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:07 UTC