W3C home > Mailing lists > Public > www-style@w3.org > January 2010

Re: Text selector [was Re: breaking overflow]

From: James Hopkins <james@idreamincode.co.uk>
Date: Mon, 4 Jan 2010 07:39:34 +0000
Message-Id: <7861A56C-23AB-45A0-AC6F-DB1C6882E261@idreamincode.co.uk>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
Cc: www-style list <www-style@w3.org>
>> If "bar" is split over two adjacent text nodes (e.g "b ar"), it  
>> could be
>> matched by ::text(b ar){}.
> I'm not sure I follow.  ::text(b ar) would match the string "b  
> ar" (with a space in it), no?

Indeed, which is what my 'for example' ("b ar") aimed to demonstrate :)

>> I personally can't envisage a use case where crossing textnodes (or
>> element boundaries, for that matter) in order to match a single word,
>> would be beneficial.
> Really?  Textnode boundaries can come in arbitrary places in text  
> (more on this in my upcoming reply to Brad in this thread).

My aim is to answer these in a separate email.

> Element boundaries happen in the middle of words all the time right  
> now; whether that's because sites are trying to apply particular  
> styling to parts of words

After some more thought, I retract my earlier opinion; it makes  
complete sense to cross element boundaries for the styling reason alone.
Received on Monday, 4 January 2010 07:40:04 UTC

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