Re: [Selectors4] Define Selectors in terms of the DOM

On Sun, 24 Jul 2011 17:13:33 -0700, Tab Atkins Jr. <>  
> There are several instances of Selectors being used on non-DOM
> structures.  For example, WebVTT, or <>.
> There's no reason to exclude things like this.

1) WebVTT does not use selector matching. It defines in detail how various  
::cue(ident) map to its tree, but that has nothing to do with the selector  
model. 2) Nothing would be excluded. You just state they need a DOM or  
equivalent data model.

> What's the benefit of adopting the DOM as the data model?  The current
> element-tree is almost the same thing; an element is just a thing with
> a type, an id, a bag of classes, a bag of attribute key/value pairs,
> and an arbitrary set of pseudo-classes.  That's basically just the DOM
> notion of an element, minus anything irrelevant for Selectors.

There is no current element-tree.

Anne van Kesteren

Received on Monday, 25 July 2011 15:23:57 UTC