Re: Are we in favour of implementing the client hints header?

2016-03-22 Thread Ilya Grigorik
On Tue, Mar 8, 2016 at 5:05 AM, Xidorn Quan wrote: > So it seems there were some websites tried to use this, which made its > usage up to 0.06%, but then they abandoned. All of the features above is > used only in ~0.0002% of pages surveyed now, which may indicate its > unpopularity. Not sure why

Re: Intent to implement: Frame Timing API

2015-05-11 Thread Ilya Grigorik
FWIW, we have a tracking issue for this on GH: https://github.com/w3c/frame-timing/issues/40 On Mon, May 11, 2015 at 12:58 PM, Boris Zbarsky wrote: > No, you can't. We explicitly forbid that, precisely because of > side-channel timing attacks. dbaron has a good writeup about how the > :visited

Re: Intent to Implement: User Timing API

2014-12-12 Thread Ilya Grigorik
\o/ On Thu, Dec 11, 2014 at 5:15 PM, Jonas Sicking wrote: > Yes! > > On Thu, Dec 11, 2014 at 5:11 PM, Kyle Machulis > wrote: > > Summary: We've already got the performance resource timing API > implemented (https://bugzilla.mozilla.org/show_bug.cgi?id=822480), but > never got around to implemen

Re: Intent to implement: WOFF2 webfont format

2014-10-02 Thread Ilya Grigorik
On Thursday, October 2, 2014 9:17:38 AM UTC-7, Ehsan Akhgari wrote: > On 2014-10-02, 7:03 AM, Jonathan Kew wrote: > > > > WOFF2 is currently supported by Chrome and Opera,[4] and the Google > > webfonts service is serving WOFF2-compressed fonts to browser versions > > that are known to support it

Re: Intent to implement: Prerendering API

2014-08-13 Thread Ilya Grigorik
On Wed, Aug 13, 2014 at 5:16 PM, Jonas Sicking wrote: > On Wed, Aug 13, 2014 at 12:24 PM, Ilya Grigorik > wrote: > > On Tue, Aug 12, 2014 at 3:17 PM, Jonas Sicking wrote: > > Do you really think that Google would be able to morph a google > calendar page into the goog

Re: Intent to implement: Prerendering API

2014-08-13 Thread Ilya Grigorik
On Tue, Aug 12, 2014 at 3:17 PM, Jonas Sicking wrote: > On Tue, Aug 12, 2014 at 1:04 PM, Ilya Grigorik > wrote: > > Whereas for (b) you can also do it in place by prefetching the template > and then issuing a data request for relevant data once you know the exact > URL... Wh

Re: Intent to implement: Prerendering API

2014-08-13 Thread Ilya Grigorik
(reposting, got stuck in the queue) On Tue, Aug 12, 2014 at 3:17 PM, Jonas Sicking wrote: > On Tue, Aug 12, 2014 at 1:04 PM, Ilya Grigorik > wrote: > > Whereas for (b) you can also do it in place by prefetching the template > and then issuing a data request for relevant data on

Re: Intent to implement: Prerendering API

2014-08-12 Thread Ilya Grigorik
On Tuesday, August 12, 2014 8:39:11 AM UTC-7, Jesper Kristensen wrote: > This templated prerendereing sounds like a complicated API. Is there any > advantage of this over what is possible today with a single page > application using history.pushState? I'm still trying to wrap my head around the