On Sep 3, 2013, at 3:45 AM, Jake Archibald <jaffathec...@gmail.com> wrote:
> On 31 August 2013 00:04, Ryosuke Niwa <rn...@apple.com> wrote: > >> It'll be much harder to implement a new dependency API that replies on CSS >> selectors if we care about the performance at all. >> > > Where does the performance issue come from? It would only need to be > resolved once on node creation or insertion into the document (the latter > of the two). It's only used for execution, downloads can still be triggered > without resolving the selectors (eg, by a pre-scanner). >From the fact selector matching is slow. I'm opposed to adding selector >dependency unless there is a very important use case that can't be addressed >by referring to a script by an element id or a script filename. - R. Niwa
