W3C home > Mailing lists > Public > www-style@w3.org > August 2012

Re: Pseudo-element proposal

From: Alan Stearns <stearns@adobe.com>
Date: Tue, 7 Aug 2012 14:25:34 -0700
To: François REMY <fremycompany_pub@yahoo.fr>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <CC46D311.1428E%stearns@adobe.com>
On 8/7/12 2:08 PM, "François REMY" <fremycompany_pub@yahoo.fr> wrote:

>|  From: Alan Stearns
>|  >Secondly, when pseudo-elements are inserted or removed,
>|  >the reordering can become a nightmare.
>|  That's one problem that ordinals are meant to solve. If you know that
>|  pseudo-elements will be inserted or removed, you can choose ordinal
>|  spacing that allows for these changes without having to re-order
>|  everything. In your proposal to add slots to the content attribute,
>|  re-ordering can only be achieved by changing the entire content
>|  You have to re-order everything to make a single insertion or removal,
>|  which seems more nightmarish to me.
>I don't know which kind of metric you're using for that kind of purpose.
>myself, I use the "number of spot changes" one (I count the number of
>where I've to move the textedit cursor to in order to make a change). The
>number of spot changes is largely in favor of class names.

As I said, if you know that you will be inserting or removing
pseudo-elements, you can choose ordinal spacing that allows you to make
those changes without the extra editing steps you're counting.

For example, your first step might be to add your first pseudo-element
with ::before(10). Now if you need to add more pseudo-elements in between
that pseudo-element and the content boundary, you have nine slots to work
with before you have to re-order everything.

And I'm not sure how adding slots via the content attribute would work
across multiple style sheets. What happens if I have style sheet A that
adds one pseudo-element and style sheet B that wants to add another? One
of the content attributes would need to incorporate the other.


Received on Tuesday, 7 August 2012 21:26:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:02 UTC