Heh, no I just confused myself by reviewing a different I2P&S just
before sending this. Apologies to the list.
~these are not the LGTMs you are looking for hand wave~
On 8/18/21 1:22 PM, Joshua Bell wrote:
I2Ps don't need any LGTMs. Was there specific feedback you were
looking for?
On Wed, Aug 18, 2021 at 10:10 AM Mike Taylor <miketa...@chromium.org
<mailto:miketa...@chromium.org>> wrote:
This I2P seems to have fallen through the cracks (understandably
lots of vacation happening this month).
Any thoughts from API owners?
On 8/9/21 2:20 PM, Ari Chivukula wrote:
*
Contact emails
aric...@chromium.org <mailto:aric...@chromium.org>,
jadekess...@chromium.org
<mailto:jadekess...@chromium.org>, miketa...@chromium.org
<mailto:miketa...@chromium.org>
Design Doc
https://docs.google.com/document/d/1yhVLyEIpDhhDQf698WkvXBiPcLwxEgCBI4o1FjvXwfM/edit
<https://docs.google.com/document/d/1yhVLyEIpDhhDQf698WkvXBiPcLwxEgCBI4o1FjvXwfM/edit>
Specification
https://wicg.github.io/client-hints-infrastructure/
<https://wicg.github.io/client-hints-infrastructure/>
https://wicg.github.io/responsive-image-client-hints/
<https://wicg.github.io/responsive-image-client-hints/>
https://wicg.github.io/savedata/#save-data-request-header-field
<https://wicg.github.io/savedata/#save-data-request-header-field>
https://wicg.github.io/netinfo/#networkinformation-interface
<https://wicg.github.io/netinfo/#networkinformation-interface>
Summary
This proposal seeks to align our implementation with the
Client Hint proposal
<https://wicg.github.io/client-hints-infrastructure/>by
adding the `sec-ch-` prefix where it’s missing.
Blink component
Privacy>Fingerprinting
<https://bugs.chromium.org/p/chromium/issues/list?q=component%3APrivacy%3EFingerprinting>
Motivation
Client Hints
<https://www.chromestatus.com/feature/5995832180473856>,
a method to request information about the user's device
or conditions, have been implemented in Chrome, but since
the initial implementation the naming scheme has changed.
If implemented, this proposal would add new client hints
with a `sec-ch-` prefix to re-implement the following:
`dpr`, `width`, `viewport-width`, `device-memory`, `rtt`,
`downlink`, and `ect`.
TAG review
Not needed
*
Risks
*
Only Blink implements client hints and we are not (yet)
removing any current ones, just re-implementing existing
ones under the correct name. If usage permits, we will
remove the legacy names in the future.
*
Interoperability and Compatibility
Gecko: Client hints not implemented
WebKit: Client hints not implemented
Web developers: Positive interest from Cloudinary
<https://discourse.wicg.io/t/responsive-image-client-hints-call-for-review/5470>
Is this feature fully tested by web-platform-tests?
Yes
<https://chromium.googlesource.com/chromium/src/+/refs/heads/main/third_party/blink/web_tests/external/wpt/client-hints/>
Tracking bug
https://crbug.com/1227043 <https://crbug.com/1227043>
Link to entry on the Chrome Platform Status
https://www.chromestatus.com/feature/6658223894429696
<https://www.chromestatus.com/feature/6658223894429696>
--
You received this message because you are subscribed to the Google
Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to blink-dev+unsubscr...@chromium.org
<mailto:blink-dev+unsubscr...@chromium.org>.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7162dcb1-279f-b0f6-4502-6ceb1013980d%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/7162dcb1-279f-b0f6-4502-6ceb1013980d%40chromium.org?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/ea32a499-a417-6fbf-918a-46b5f62c3910%40chromium.org.
