Re: [webkit-dev] Client Hints

On Wed, May 6, 2015 at 9:09 PM, Maciej Stachowiak wrote: > > Some more questions/comments about RW: > > - Is maybe-image-width-maybe-viewport-width a useful value? Perhaps there > should be an always-present header for viewport width, and one for resource > width that is present only when known?

Re: [webkit-dev] Client Hints

> On May 6, 2015, at 4:49 AM, Yoav Weiss wrote: > > > > On Wed, May 6, 2015 at 8:41 AM, Ryosuke Niwa > wrote: > On Tue, May 5, 2015 at 11:35 PM, Yoav Weiss > wrote: > On Wed, May 6, 2015 at 8:14 AM, Ryosuke Niwa > wrote:

Re: [webkit-dev] Client Hints

On Wed, May 6, 2015 at 8:41 AM, Ryosuke Niwa wrote: > On Tue, May 5, 2015 at 11:35 PM, Yoav Weiss wrote: > >> On Wed, May 6, 2015 at 8:14 AM, Ryosuke Niwa wrote: >> >>> I do have the same concern over terse names. I don't see any point in >>> saving 13 bytes by abbrebiating DevicePixelRadio as

Re: [webkit-dev] Client Hints

On Tue, May 5, 2015 at 11:35 PM, Yoav Weiss wrote: > On Wed, May 6, 2015 at 8:14 AM, Ryosuke Niwa wrote: > >> I do have the same concern over terse names. I don't see any point in >> saving 13 bytes by abbrebiating DevicePixelRadio as DPR. >> >> In the case of ResourceWidth, we can't get this n

Re: [webkit-dev] Client Hints

On Wed, May 6, 2015 at 8:14 AM, Ryosuke Niwa wrote: > I do have the same concern over terse names. I don't see any point in > saving 13 bytes by abbrebiating DevicePixelRadio as DPR. > > In the case of ResourceWidth, we can't get this number until we trigger a > layout. It doesn't seem desirabl

Re: [webkit-dev] Client Hints

I do have the same concern over terse names. I don't see any point in saving 13 bytes by abbrebiating DevicePixelRadio as DPR. In the case of ResourceWidth, we can't get this number until we trigger a layout. It doesn't seem desirable to slow down the page load speed by eagering triggering layou

Re: [webkit-dev] Client Hints

Does anyone else in the WebKit community have comments on this proposal? - Maciej > On Apr 28, 2015, at 8:42 AM, Yoav Weiss wrote: > > (Re) Posting Ilya's response from April 24th, since his response wasn't > published on the mailing list archive for some reason. > > On Thu, Apr 23, 2015 a

Re: [webkit-dev] Client Hints

And (Re) Posting Mark's response from April 25th, for the same reasons. > On 24 Apr 2015, at 2:32 pm, Ilya Grigorik wrote: > > On Thu, Apr 23, 2015 at 7:02 PM, Maciej Stachowiak wrote: >> Is the Internet-Draft for this planned to become a standards-track RFC? Is there an IETF Working Group that

Re: [webkit-dev] Client Hints

(Re) Posting Ilya's response from April 24th, since his response wasn't published on the mailing list archive for some reason. On Thu, Apr 23, 2015 at 1:37 PM, Yoav Weiss wrote: > +Ilya for spec related questions. > > Also, I forgot to mention it, but my intention is to implement the RW and > DP

Re: [webkit-dev] Client Hints

(reposting to list due to missing subscription on this alias - woops! :)) On Fri, Apr 24, 2015 at 2:32 PM, Ilya Grigorik wrote: > On Thu, Apr 23, 2015 at 1:37 PM, Yoav Weiss wrote: > >> +Ilya for spec related questions. >> >> Also, I forgot to mention it, but my intention is to implement the RW

Re: [webkit-dev] Client Hints

+Ilya for spec related questions. Also, I forgot to mention it, but my intention is to implement the RW and DPR hints first, and see about the MD and RQ hints (which are newer to the spec) later on. On Thu, Apr 23, 2015 at 7:02 PM, Maciej Stachowiak wrote: > > Additional spec concerns: > > (1)

Re: [webkit-dev] Client Hints

Additional spec concerns: (1) The RW header is unimplementable because image requests are sent before the display width of the image is known. (2) The MD header is defined in a way that’s probably not useful to rely on; if I’m on 802.11g on a home WiFi network where the next hop is a cable mod

Re: [webkit-dev] Client Hints

> On Apr 23, 2015, at 12:48 AM, Yoav Weiss wrote: > > Hi, > > As I've discussed during my session at the contributor's meetup, I'm > interested in implementing Client-Hints > in WebKit. > > For those unfamiliar with it, Client-Hints is a standa

[webkit-dev] Client Hints

Hi, As I've discussed during my session at the contributor's meetup, I'm interested in implementing Client-Hints in WebKit. For those unfamiliar with it, Client-Hints is a standard destined to improve content negotiation, and enable the browser to a