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

Re: Text selector [was Re: breaking overflow]

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 8 Jan 2010 13:36:23 -0600
Message-ID: <dd0fbad1001081136g29c38a14mc90b89df6c6a2b2a@mail.gmail.com>
To: "Belov, Charles" <Charles.Belov@sfmta.com>
Cc: www-style list <www-style@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>, Brad Kemper <brad.kemper@gmail.com>, Aryeh Gregor <Simetrical+w3c@gmail.com>, James Hopkins <james@idreamincode.co.uk>
On Fri, Jan 8, 2010 at 1:17 PM, Belov, Charles <Charles.Belov@sfmta.com> wrote:
> -----Original Message-----
> From: www-style-request@w3.org [mailto:www-style-request@w3.org] On
> Behalf Of Aryeh
> On Mon, Jan 4, 2010 at 1:28 PM, James Hopkins <james@idreamincode.co.uk>
> wrote:
>>If a text node is split across two packets, apparently browsers will
> split it into two >text nodes, at least sometimes.  Obviously, having
> behavior change noticeably because
>>of that would be a really bad idea, since it's not feasible to control
> where packet
>>boundaries are.
> Then one of the user agent requirements for supporting the ::text
> pseudoselector would be that if a style sheet in the cascade used such a
> selector the browser would have to first patch together any text node
> that it had previously arbitrarily split.
> That would be a programming issue rather than a CSS issue, but it is
> good to know that user-agent programmers would have to look for it.
> There would need to be a way for programmers to intentionally construct
> such packets for testing purposes, but I would imagine that is doable.

It shouldn't be necessary to test for this specifically.  A split text
node doesn't know *why* it was split, and neither does the CSS engine
attempting to match against it.  As long as you can manufacture a
split text node through some means, such as DOM scripting, you should
be good.

Received on Friday, 8 January 2010 19:36:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:31 UTC