W3C home > Mailing lists > Public > public-web-perf@w3.org > August 2016

Re: Long Tasks Notifications API

From: Ilya Grigorik <igrigorik@google.com>
Date: Fri, 5 Aug 2016 15:37:20 -0700
Message-ID: <CADXXVKqn6fQA_kTkjX11q9pWKj7b22WkJSP=tnysexGvshTwQw@mail.gmail.com>
To: Shubhie Panicker <panicker@google.com>
Cc: Ben Maurer <ben.maurer@gmail.com>, public-web-perf <public-web-perf@w3.org>, Nat Duca <nduca@google.com>
On Fri, Aug 5, 2016 at 3:22 PM, Shubhie Panicker <panicker@google.com>
wrote:

> - Re: extensions
> We *may* be able to indicate something generic here. Prior investigation
> <https://codereview.chromium.org/1615523002/> indicates that it's very
> difficult to properly account for scripts spawned by extensions.
>

I think we want to be really careful with this one.. Yes, extensions can
definitely affect runtime of the page, both in the early stages of the page
load and while the page is active, and it would be nice to get a handle on
that. However, we can't simply expose which extensions (e.g. script urls
and related bits) the user is running due to security/privacy concerns.

It's a problem worth thinking about, but I would mark it as an explicit
non-goal for the v1 we're discussing here..
Received on Friday, 5 August 2016 22:38:30 UTC

This archive was generated by hypermail 2.3.1 : Sunday, 18 September 2016 16:33:38 UTC