W3C home > Mailing lists > Public > www-style@w3.org > September 2008

Re: [css3-gcpm] new editor's draft; page lists, page floats, text-replace

From: Håkon Wium Lie <howcome@opera.com>
Date: Wed, 3 Sep 2008 19:17:43 +0200
Message-ID: <18622.50871.463792.670675@opera.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: www-style@w3.org

Also sprach Tab Atkins Jr.:

 > >  - text-replace: there was a debate at the F2f whether (a) this
 > >    funcionality should be offered as part of CSS, or (b) if it can be
 > >    expressed in a different way. Here is one possible solution:
 > >
 > >       *:text("Soviet Union") { content: "Russia" }
 > >
 > >    which, potentiall, could be even mover powerful:
 > >
 > >       *:text("Soviet Union") { content: "Russia"; color: red }

 > I'm not entirely sure how this is supposed to work.  Is the :text
 > pseudoclass meant to match only if the element contains *only* that text and
 > nothing else?  That seems to be the only way to square it with the operation
 > of the content: property.  It also makes it fairly useless.  It would likely
 > be more sensical to use a ::text() pseudoelement.

Yes, it's meant to be a pseudo-element -- the pseuo-element is
generated on the spot if the text matches. I've added another ":" in
the selector.

 > I'm assuming that this doesn't cross element boundaries either, as I think
 > that was the reason why a very similar proposal was dropped from an earlier
 > draft of Selectors.  This makes the operator somewhat fragile for its
 > intended purpose.

Agree.

-h&kon
              Håkon Wium Lie                          CTO °þe®ª
howcome@opera.com                  http://people.opera.com/howcome
Received on Wednesday, 3 September 2008 17:18:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:55:12 GMT