- From: Ilya Grigorik <igrigorik@google.com>
- Date: Wed, 30 Apr 2014 12:23:55 -0700
- To: Tobin Titus <tobint@microsoft.com>
- Cc: Arvind Jain <arvind@google.com>, public-web-perf <public-web-perf@w3.org>
Received on Wednesday, 30 April 2014 19:25:03 UTC
Hi Tobin. I did a quick informal poll with Chrome folks, and the feedback is pretty one-sided: - the use case is not compelling / not seen as critical. - it doesn't seem like this is a problem the browser needs to be solving. - complicated mechanism (yet another cookie). For more comprehensive feedback I'd suggest starting a thread on blink-dev@, but based on what I've heard I'd mark it as a no-go for Chrome. ig On Fri, Apr 25, 2014 at 3:20 PM, Ilya Grigorik <igrigorik@google.com> wrote: > Hi Tobin. Thanks for the reminder, let me gather some feedback.. stay > tuned. > > ig > > > On Wed, Apr 23, 2014 at 1:17 PM, Tobin Titus <tobint@microsoft.com> wrote: > >> Ilya and Arvind, >> >> >> >> There are a couple of open actions on the web performance working group >> around getting feedback on Preflight Injection. The open action to request >> feedback from Google is here: >> http://www.w3.org/2010/webperf/track/actions/120 >> >> >> >> >> >> The specification can be found here: >> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/JSPreflightInjection/Overview.html >> >> >> >> I just wanted to request that you take a look to see if you’ve got >> thoughts. >> >> >> >> Thanks in advance. >> >> >> >> Tobin Titus >> >> >> > >
Received on Wednesday, 30 April 2014 19:25:03 UTC