23788 2013-11-11 07:12:14 +0000 Update link to CSS selector spec and consider including :current 2014-02-13 10:41:06 +0000 1 1 1 Unclassified TextTracks CG WebVTT unspecified PC All NEW v2 P2 normal --- 1 silviapfeiffer1 silviapfeiffer1 fantasai.bugs mike philipj public-texttracks dave.null oldest_to_newest 96109 0 silviapfeiffer1 2013-11-11 07:12:14 +0000 fantasai suggested pointing to TR: http://www.w3.org/TR/selectors4/ and consider including the :current pseudo-class http://www.w3.org/TR/selectors4/#current-pseudo 99317 1 philipj 2014-01-28 17:43:52 +0000 fantasai, is there any particular reason we should use TR instead of the latest spec? The selectors4 TR is from 2 May 2013, while the ED was updated yesterday. Living Standards, and all that. I don't think I understand :current, cue timestamps are not ranges, so they will either be in the past or in the future. How would :current work in WebVTT? 99500 2 silviapfeiffer1 2014-01-30 21:44:46 +0000 From an author viewpoint, I can imagine that the "current" text is highlighted (say in red) while the past is greyed out and the future is black. If :current falls between words, it could be a position indicator (similar to a cursor), e.g. a red cursor in the above example. 99513 3 fantasai.bugs 2014-01-31 00:30:28 +0000 The CSSWG's official specs are the ones hosted on /TR. We could be better about updating them, but an ED is considered unofficial until we take a resolution to publish. The changes between the Selectors ED and WD at the moment aren't particularly substantial, just a few clarifications. Someday when the W3C publication process is fixed up, /TR will be more up-to-date, because we'll push resolved changes through immediately instead of batching them as we do currently. :) 100488 4 silviapfeiffer1 2014-02-13 10:41:06 +0000 Fixed the reference: https://github.com/w3c/webvtt/commit/cd0c0a2c06f38dd488163f218a7c5e89a61707a0 I'm leaving the bug open for v2 for :current . I think the use case for WebVTT needs to be discussed a bit further.