- From: Eric Portis <notifications@github.com>
- Date: Thu, 24 Jan 2019 07:57:26 -0800
- To: whatwg/fetch <fetch@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/fetch/pull/773/review/196106796@github.com>
eeeps commented on this pull request. > + <dt>`<code>Width</code>` + <dd>a suitable <a href=http://httpwg.org/http-extensions/client-hints.html#width>width value</a> + <dt>`<code>Device-Memory</code>` + <dd>a suitable <a href=https://w3c.github.io/device-memory/#sec-device-memory-client-hint-header>Device-Memory value</a> + <dt>`<code>RTT</code>` + <dd>a suitable <a href=https://wicg.github.io/netinfo/#rtt-request-header-field>RTT value</a> + <dt>`<code>Downlink</code>` + <dd>a suitable <a href=https://wicg.github.io/netinfo/#downlink-request-header-field>Downlink value</a> + <dt>`<code>ECT</code>` + <dd>a suitable <a href=https://wicg.github.io/netinfo/#ect-request-header-field>ECT value</a> + </dl> + + <li><p>If <var>request</var> is a <a>subresource request</a> and the result of running <a + href="https://wicg.github.io/feature-policy/#should-request-be-allowed-to-use-feature">Should + request be allowed to use feature?</a>, given <var>request</var> and <var>hintName</var>’s + <a href="http://httpwg.org/http-extensions/client-hints.html#opt-in-via-feature-policy">associated Reading the discussion on the relevant PR over in the Client Hints spec (https://github.com/httpwg/http-extensions/pull/696), I don't think the definitions of the policy-controlled features that we're linking to here will be landing there. We need to find a new place for those definitions to live, and change this link. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/fetch/pull/773#pullrequestreview-196106796
Received on Thursday, 24 January 2019 15:57:48 UTC