W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2013

Re: [whatwg] Script preloading

From: Ryosuke Niwa <rniwa@apple.com>
Date: Tue, 03 Sep 2013 11:27:44 -0700
Message-id: <C7FE4CCA-19EA-4544-B14B-19295C4DB9ED@apple.com>
To: Jake Archibald <jaffathecake@gmail.com>
Cc: "whatwg@whatwg.org" <whatwg@whatwg.org>, Yoav Weiss <yoav@yoav.ws>, Ian Hickson <ian@hixie.ch>
On Sep 3, 2013, at 3:45 AM, Jake Archibald <jaffathecake@gmail.com> wrote:

> On 31 August 2013 00:04, Ryosuke Niwa <rniwa@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
Received on Tuesday, 3 September 2013 18:28:18 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:09 UTC