W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2016

Re: draft-ietf-httpbis-client-hints-00 feedback

From: Matthew Kerwin <matthew@kerwin.net.au>
Date: Wed, 30 Mar 2016 23:23:15 +1000
Message-ID: <CACweHNDxNdFkkoK=+cQE1RrKwwYLPFUbxMyiLtjKecSrWH+tFg@mail.gmail.com>
To: Ilya Grigorik <igrigorik@gmail.com>
Cc: ietf-http-wg@w3.org, Julian Reschke <julian.reschke@gmx.de>
On 30/03/2016 12:45 PM, "Ilya Grigorik" <igrigorik@gmail.com> wrote:
>
>
> On Tue, Mar 29, 2016 at 11:38 AM, Julian Reschke <julian.reschke@gmx.de>
wrote:
>>
>> [snip]
>>
>> 4.  The Width Client Hint
>>
>>    The "Width" header field is a number that, in requests, indicates the
>>    resource width in physical px (i.e. intrinsic size of an image).  The
>>    provided physical px value is a number rounded to the largest
>>    smallest following integer (i.e. ceiling value).
>>
>>
>>      Width = 1*DIGIT
>>
>>    If the resource width is not known at the time of the request or the
>>    resource does not have a display width, the Width header field may be
>>    omitted.  If Width occurs in a message more than once, the last value
>>    overrides all previous occurrences.
>>
>> It took me some time to understand that this is the width the user agent
intends to use to display the resource. Maybe this could be rephrased.
>
>
> Hmm, no. Physical width != display width. For example, on a "2x" screen a
100 (CSS) px resource has an intrinsic size of 200px. FWIW, this language
follows CSS spec, and I'd prefer to keep it aligned.
>

I think the point is that the browser seems to be telling the server how
big a requested image will be, which is ...presumptive. What it's actually
describing is the screen space it intends to fill with said image.

Unless "resource" means something else in the context of a HTML document?
Since this is a HTTP spec, I took it to mean "thing at the other end of a
URL."

Perhaps just one extra word is enough: "...indicates the desired resource
width..."

>> [snip]
>>
>> 10.  IANA Considerations
>>
>>    o  Header field name: DPR
>>    o  Applicable protocol: HTTP
>>    o  Status: standard
>>    o  Author/Change controller: IETF
>>    o  Specification document(s): [this document]
>>
>> ...insert section # (applies to all definitions)
>
>
> Hmm, does our tooling allow us to auto-generate these? =/
>

Yep; you label the heading thus:

### Foo Bar {#foo-bar}

And refer to it:

...described in {{foo-bar}}...

Cheers
Received on Wednesday, 30 March 2016 13:23:46 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 30 March 2016 13:23:49 UTC