- From: Simon Pieters <simonp@opera.com>
- Date: Tue, 25 Jun 2013 19:39:34 +0200
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- Cc: "Dimitri Glazkov" <dglazkov@google.com>, "Hayato Ito" <hayato@google.com>, "Boris Zbarsky" <bzbarsky@mit.edu>, "Jonas Sicking" <jonas@sicking.cc>, "William Chen" <wchen@mozilla.com>, "Blake Kaplan" <mrbkap@mozilla.com>, "Daniel Buchner" <daniel@mozilla.com>, "Dominic Cooney" <dominicc@chromium.org>, "Takashi Sakamoto" <tasak@google.com>, "public-texttracks@w3.org" <public-texttracks@w3.org>
-public-webapps
+public-texttracks
context:
http://www.w3.org/mid/CAAWBYDAuoHeP2bLC-78bmqw_dnQyD0mpWWWwBXa-1uya0AXxzg@mail.gmail.com
On Tue, 25 Jun 2013 19:30:29 +0200, Tab Atkins Jr. <jackalmage@gmail.com>
wrote:
>> So it can contain commas...
>
> Yes. Note that this is the :host() pseudo-class, and will stay
> functional. (Just making sure you're not accidentally conflating it
> with ::content, down below.)
Ah. I missed that.
>> There's also ::cue().
>>
>> I don't understand how this idiom is supposed to work when you have a
>> list
>> of selectors as argument. Consider:
>>
>> video::cue(b, i) { background:lime }
>>
>> If it's changed to
>>
>> video::cue b, i { background:lime }
>>
>> then that looks like there are two selectors, "video::cue b" and "i".
>
> Just use the existing CSS tools for indicating choice within a selector:
>
> video::cue :matches(b, i) {...}
OK. So should we change ::cue(foo) to ::cue foo?
--
Simon Pieters
Opera Software
Received on Tuesday, 25 June 2013 17:38:01 UTC