- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 17 Jan 2014 09:58:28 -0800
- To: Simon Sapin <simon.sapin@exyr.org>
- Cc: www-style <www-style@w3.org>
On Fri, Jan 17, 2014 at 2:00 AM, Simon Sapin <simon.sapin@exyr.org> wrote: > Hi, > > I find the current definitions of :current and other time-dimensional > pseudo-classes a bit misleading: > >> The :current pseudo-class represents the element, or an ancestor of >> the element, that is currently being displayed. > > > > There are tons of slideshow systems out there based on HTML and JavaScript, > where each slide is an HTML element. At any time, there is one slide being > displayed, which matches perfectly the definition of :current. > > But :current does not match any element in this case, because web browsers > do not implement it that way. (They don’t really know about the > JavaScript-constructed "timeline" of slides.) > > > I suggest clarifying that these pseudo-classes depend on a timeline, and do > not match anything unless the UA supports another spec (such as WebVTT) that > defines such a timeline. > > (This is similar to how Selectors depends on other specs to define "the > language of a element" for :lang().) The opening paragraph of the section already implied this, but you're right that it needed to be clearer. I've added a further paragraph about this. ~TJ
Received on Friday, 17 January 2014 17:59:14 UTC