This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28237 - [WebVTT] Should :past and :future pseudo-classes be each others negations?
Summary: [WebVTT] Should :past and :future pseudo-classes be each others negations?
Status: NEW
Alias: None
Product: TextTracks CG
Classification: Unclassified
Component: WebVTT (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: Web Media Text Tracks CG
URL: http://dev.w3.org/html5/webvtt/
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-19 08:50 UTC by Philip Jägenstedt
Modified: 2015-04-19 03:15 UTC (History)
5 users (show)

See Also:
philipj: needinfo? (eric.carlson)

Attachments

Description Philip Jägenstedt 2015-03-19 08:50:11 UTC 
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.)
Comment 1 Philip Jägenstedt 2015-03-19 08:55:20 UTC 
Fixed title to be less wrong. :past and :future are mutually exclusive per spec as well, but it's possible for neither to match.
Comment 2 Simon Pieters 2015-03-19 11:55:46 UTC 
(In reply to Philip Jägenstedt from comment #0)
> What is most useful for developers?

See https://www.w3.org/Bugs/Public/show_bug.cgi?id=16875
Comment 3 Philip Jägenstedt 2015-03-19 12:12:43 UTC 
(In reply to Simon Pieters from comment #2)
> (In reply to Philip Jägenstedt from comment #0)
> > What is most useful for developers?
> 
> See https://www.w3.org/Bugs/Public/show_bug.cgi?id=16875

Any comment in particular? I agree that it's a problem, more serious than this bug, but it they seem like orthogonal problems to me.
Comment 4 Simon Pieters 2015-03-19 13:10:20 UTC 
I was thinking that fixing that bug might make this bug moot, but it depends on what the fix is.
Comment 5 Philip Jägenstedt 2015-03-20 05:38:12 UTC 
Eric, WebKit is also affected by this.

Fredrik and I think doing what the spec currently says seems fine, does that sound OK to you?