[Bug 28237] New: Should :past and :future pseudo-classes be mutually exclusive

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28237

            Bug ID: 28237
           Summary: Should :past and :future pseudo-classes be mutually
                    exclusive
           Product: TextTracks CG
           Version: unspecified
          Hardware: PC
               URL: http://dev.w3.org/html5/webvtt/
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebVTT
          Assignee: dave.null@w3.org
          Reporter: philipj@opera.com
        QA Contact: public-texttracks@w3.org
                CC: philipj@opera.com, silviapfeiffer1@gmail.com

As implemented in Blink and WebKit, :past is equivalent to :not(:future) and
vice versa. This is not per spec, where :past and :future will only match if
there's a timestamp node somewhere in the cue.

What do other implementations do? What is most useful for developers?

(Note that Blink's implementation makes it possible to only traverse the nodes
once, where the spec's implementation would make it moderately more complex.)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 19 March 2015 08:50:13 UTC