Re: [blink-dev] Intent to Ship: Viewport-height client hint

2022-07-12 Thread 'Max Curran' via blink-dev 
Yes, the plan is to ship in 105

On Mon, Jul 11, 2022 at 8:06 AM Joe Medley  wrote:

> Is this shipping in 105?
> Joe Medley | Technical Writer, Chrome DevRel | jmed...@google.com |
> 816-678-7195 <(816)%20678-7195>
> *If an API's not documented it doesn't exist.*
>
>
> On Thu, Jun 30, 2022 at 1:38 PM Yoav Weiss  wrote:
>
>> LGTM3
>>
>> On Thu, Jun 30, 2022 at 10:33 PM Chris Harrelson 
>> wrote:
>>
>>> LGTM2
>>>
>>> On Thu, Jun 30, 2022 at 1:32 PM Mike Taylor 
>>> wrote:
>>>
>>>> Thanks for the update.
>>>>
>>>> LGTM1 to ship. This seems like a useful addition to the Viewport-Width
>>>> hint.
>>>>
>>>> On 6/30/22 12:59 PM, 'Max Curran' via blink-dev wrote:
>>>>
>>>> Our partners found the feature useful and want to see it launched.
>>>>
>>>> On Wednesday, June 29, 2022 at 8:13:38 AM UTC-7 Daniel Bratell wrote:
>>>>
>>>>> What was the result of the origin trial? Did you get any useful
>>>>> feedback?
>>>>>
>>>>> /Daniel
>>>>> On 2022-06-27 22:15, 'Max Curran' via blink-dev wrote:
>>>>>
>>>>> Contact emails
>>>>>
>>>>> ryan...@chromium.org, curr...@chromium.org
>>>>>
>>>>> Explainer
>>>>>
>>>>>
>>>>> https://github.com/WICG/responsive-image-client-hints/blob/master/Viewport-Height-Explainer.md
>>>>>
>>>>> Specification
>>>>>
>>>>>
>>>>> https://wicg.github.io/responsive-image-client-hints/#sec-ch-viewport-height
>>>>>
>>>>> Summary
>>>>>
>>>>> Currently, Responsive Image Client Hints provide a way for origins to
>>>>> obtain the viewport’s width. However, no such attribute exists for 
>>>>> viewport
>>>>> height. We’ve observed that to optimize the loading of content that 
>>>>> appears
>>>>> in viewport, it is essential for the origins to adapt HTML response based
>>>>> on viewport height.
>>>>>
>>>>>
>>>>> Blink component
>>>>>
>>>>> Blink>Loader
>>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELoader>
>>>>>
>>>>> TAG review
>>>>>
>>>>> https://github.com/w3ctag/design-reviews/issues/615
>>>>>
>>>>> TAG review status
>>>>>
>>>>> Issues addressed
>>>>>
>>>>> Link to origin trial feedback summary
>>>>>
>>>>> https://github.com/WICG/responsive-image-client-hints/issues
>>>>>
>>>>> Risks
>>>>>
>>>>> Interoperability and Compatibility
>>>>>
>>>>> Gecko: No signal (
>>>>> https://github.com/mozilla/standards-positions/issues/79)
>>>>>
>>>>> WebKit: Negative (
>>>>> https://lists.webkit.org/pipermail/webkit-dev/2020-November/031576.html)
>>>>> Likely to be neutral based on discussion in
>>>>> https://github.com/mozilla/standards-positions/issues/79
>>>>>
>>>>> Web developers: No signals
>>>>>
>>>>> Other signals:
>>>>>
>>>>> Activation
>>>>>
>>>>> None
>>>>>
>>>>>
>>>>> WebView application risks
>>>>>
>>>>> Does this intent deprecate or change behavior of existing APIs, such
>>>>> that it has potentially high risk for Android WebView-based applications?
>>>>>
>>>>>
>>>>> Debuggability
>>>>>
>>>>> N/A
>>>>>
>>>>>
>>>>> Will this feature be supported on all six Blink platforms (Windows,
>>>>> Mac, Linux, Chrome OS, Android, and Android WebView)?
>>>>>
>>>>> Yes
>>>>>
>>>>> Is this feature fully tested by web-platform-tests
>>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>>>>> ?
>>>>>
>>>>> Yes
>>>>>
>>>>> Flag name
>>>>>
>>>>> kViewportHeightClientHintHeader
>>>>>
>>>>> Requ

Re: [blink-dev] Intent to Ship: Viewport-height client hint

2022-06-30 Thread 'Max Curran' via blink-dev 
Our partners found the feature useful and want to see it launched.

On Wednesday, June 29, 2022 at 8:13:38 AM UTC-7 Daniel Bratell wrote:

> What was the result of the origin trial? Did you get any useful feedback?
>
> /Daniel
> On 2022-06-27 22:15, 'Max Curran' via blink-dev wrote:
>
> Contact emails 
>
> ryan...@chromium.org, curr...@chromium.org
>
> Explainer 
>
>
> https://github.com/WICG/responsive-image-client-hints/blob/master/Viewport-Height-Explainer.md
>
> Specification 
>
>
> https://wicg.github.io/responsive-image-client-hints/#sec-ch-viewport-height
>
> Summary 
>
> Currently, Responsive Image Client Hints provide a way for origins to 
> obtain the viewport’s width. However, no such attribute exists for viewport 
> height. We’ve observed that to optimize the loading of content that appears 
> in viewport, it is essential for the origins to adapt HTML response based 
> on viewport height.
>
>
> Blink component 
>
> Blink>Loader 
> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELoader>
>
> TAG review 
>
> https://github.com/w3ctag/design-reviews/issues/615
>
> TAG review status 
>
> Issues addressed
>
> Link to origin trial feedback summary 
>
> https://github.com/WICG/responsive-image-client-hints/issues
>
> Risks 
>
> Interoperability and Compatibility 
>
> Gecko: No signal (https://github.com/mozilla/standards-positions/issues/79
> )
>
> WebKit: Negative (
> https://lists.webkit.org/pipermail/webkit-dev/2020-November/031576.html) 
> Likely to be neutral based on discussion in 
> https://github.com/mozilla/standards-positions/issues/79
>
> Web developers: No signals
>
> Other signals:
>
> Activation 
>
> None
>
>
> WebView application risks 
>
> Does this intent deprecate or change behavior of existing APIs, such that 
> it has potentially high risk for Android WebView-based applications?
>
>
> Debuggability 
>
> N/A
>
>
> Will this feature be supported on all six Blink platforms (Windows, Mac, 
> Linux, Chrome OS, Android, and Android WebView)? 
>
> Yes
>
> Is this feature fully tested by web-platform-tests 
> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
> ? 
>
> Yes
>
> Flag name 
>
> kViewportHeightClientHintHeader
>
> Requires code in //chrome? 
>
> False
>
> Tracking bug 
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=1184863
>
> Launch bug 
>
> https://bugs.chromium.org/p/chromium/issues/detail?id=1184862
>
> Estimated milestones 
>
> OriginTrial desktop last
>
> 104
>
> OriginTrial desktop first
>
> 100
>
> OriginTrial Android last
>
> 104
>
> OriginTrial Android first
>
> 100
>
>
>
>
> Anticipated spec changes 
>
> Open questions about a feature may be a source of future web compat or 
> interop issues. Please list open issues (e.g. links to known github issues 
> in the project for the feature specification) whose resolution may 
> introduce web compat/interop risk (e.g., changing to naming or structure of 
> the API in a non-backward-compatible way).
>
>
> Link to entry on the Chrome Platform Status 
>
> https://chromestatus.com/feature/5646861215989760
>
> Links to previous Intent discussions 
>
> Intent to Experiment: 
> https://groups.google.com/a/chromium.org/g/blink-dev/c/Q2wcqY2UyNs/m/rPePdX_NBwAJ
>
> Intent to Extend Experiment: 
> https://groups.google.com/a/chromium.org/g/blink-dev/c/kftmeKVDjE8/m/GlaCr5PYEQAJ
>
>
> This intent message was generated by Chrome Platform Status 
> <https://chromestatus.com/>.
>
> -- 
> 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+...@chromium.org.
> To view this discussion on the web visit 
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BEneNMJuAb7K5R0Gsxp2FvcL-Ny8rTmmLR7C_WgiUiz5FNbKA%40mail.gmail.com
>  
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CA%2BEneNMJuAb7K5R0Gsxp2FvcL-Ny8rTmmLR7C_WgiUiz5FNbKA%40mail.gmail.com?utm_medium=email_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/e5d6eab0-da9a-4804-9120-5cfe164c1bf6n%40chromium.org.

[blink-dev] Intent to Ship: Viewport-height client hint

2022-06-27 Thread 'Max Curran' via blink-dev 
Contact emails

ryanst...@chromium.org, curran...@chromium.org

Explainer

https://github.com/WICG/responsive-image-client-hints/blob/master/Viewport-Height-Explainer.md

Specification

https://wicg.github.io/responsive-image-client-hints/#sec-ch-viewport-height

Summary

Currently, Responsive Image Client Hints provide a way for origins to
obtain the viewport’s width. However, no such attribute exists for viewport
height. We’ve observed that to optimize the loading of content that appears
in viewport, it is essential for the origins to adapt HTML response based
on viewport height.


Blink component

Blink>Loader


TAG review

https://github.com/w3ctag/design-reviews/issues/615

TAG review status

Issues addressed

Link to origin trial feedback summary

https://github.com/WICG/responsive-image-client-hints/issues

Risks

Interoperability and Compatibility

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/79)

WebKit: Negative (
https://lists.webkit.org/pipermail/webkit-dev/2020-November/031576.html)
Likely to be neutral based on discussion in
https://github.com/mozilla/standards-positions/issues/79

Web developers: No signals

Other signals:

Activation

None


WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that
it has potentially high risk for Android WebView-based applications?


Debuggability

N/A


Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, Chrome OS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests

?

Yes

Flag name

kViewportHeightClientHintHeader

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1184863

Launch bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1184862

Estimated milestones

OriginTrial desktop last

104

OriginTrial desktop first

100

OriginTrial Android last

104

OriginTrial Android first

100




Anticipated spec changes

Open questions about a feature may be a source of future web compat or
interop issues. Please list open issues (e.g. links to known github issues
in the project for the feature specification) whose resolution may
introduce web compat/interop risk (e.g., changing to naming or structure of
the API in a non-backward-compatible way).


Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5646861215989760

Links to previous Intent discussions

Intent to Experiment:
https://groups.google.com/a/chromium.org/g/blink-dev/c/Q2wcqY2UyNs/m/rPePdX_NBwAJ

Intent to Extend Experiment:
https://groups.google.com/a/chromium.org/g/blink-dev/c/kftmeKVDjE8/m/GlaCr5PYEQAJ


This intent message was generated by Chrome Platform Status
.

-- 
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/CA%2BEneNMJuAb7K5R0Gsxp2FvcL-Ny8rTmmLR7C_WgiUiz5FNbKA%40mail.gmail.com.

Re: [blink-dev] Intent to Experiment: Viewport-height client hint

2022-04-07 Thread 'Max Curran' via blink-dev 
We are running a coordinated experiment with Search. The Chrome side was
started in M99, but they were only able to start their side of the
experiment this week. Other than Search, no other partners have signed up.

On Thu, Apr 7, 2022 at 2:18 AM Yoav Weiss  wrote:

>
>
> On Wed, Apr 6, 2022 at 11:25 PM 'Max Curran' via blink-dev <
> blink-dev@chromium.org> wrote:
>
>> Contact emails
>>
>> curran...@chromium.org, ryanst...@chromium.org
>>
>> Explainer
>>
>>
>> https://github.com/WICG/responsive-image-client-hints/blob/master/Viewport-Height-Explainer.md
>>
>> Specification
>>
>>
>> https://wicg.github.io/responsive-image-client-hints/#sec-ch-viewport-height
>>
>> Summary
>>
>> Currently, Responsive Image Client Hints provide a way for origins to
>> obtain the viewport’s width. However, no such attribute exists for viewport
>> height. We’ve observed that to optimize the loading of content that appears
>> in viewport, it is essential for the origins to adapt HTML response based
>> on viewport height.
>>
>>
>> Blink component
>>
>> Blink>Loader
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ELoader>
>>
>> TAG review
>>
>> https://github.com/w3ctag/design-reviews/issues/615
>>
>> TAG review status
>>
>> Issues addressed
>>
>> Link to origin trial feedback summary
>>
>> https://github.com/WICG/responsive-image-client-hints/issues
>>
>> Risks
>>
>> Interoperability and Compatibility
>>
>> Gecko: No signal (
>> https://github.com/mozilla/standards-positions/issues/79)
>>
>> WebKit: Negative (
>> https://lists.webkit.org/pipermail/webkit-dev/2020-November/031576.html)
>> Likely to be neutral based on discussion in
>> https://github.com/mozilla/standards-positions/issues/79
>>
>> Web developers: No signals
>>
>> Other signals:
>>
>> Activation
>>
>> None
>>
>>
>> WebView Application Risks
>>
>> Does this intent deprecate or change behavior of existing APIs, such that
>> it has potentially high risk for Android WebView-based applications?
>>
>>
>> Goals for experimentation
>>
>> Client hints opt-ins from origins are session-sticky which makes it
>> difficult to experiment with using origin trials since origin trials
>> operate at document-level. We plan to run an A/B experiment using Chrome’s
>> field trial infrastructure. Our plan is to enable the feature for at most
>> 1% users to collect metrics, and ship this feature only if it shows
>> performance improvement for origins that choose to use this feature.
>>
>>
>> Reason this experiment is being extended
>>
>> Due to Chrome approvals taking longer than expected, and partners still
>> needing to implement how to use the client hint, we have not been able to
>> experiment yet. We would like to extend the origin trial from M101 to M104.
>>
>
> Has the experiment started in the M99 timeframe? Or are you planning to
> start it later? Have any partners signed up?
>
>
>> Ongoing technical constraints
>>
>> Debuggability
>>
>> N/A
>>
>>
>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>> Linux, Chrome OS, Android, and Android WebView)?
>>
>> Yes
>>
>> Is this feature fully tested by web-platform-tests
>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>
>> ?
>>
>> Yes
>>
>> Flag name
>>
>> kViewportHeightClientHintHeader
>>
>> Requires code in //chrome?
>>
>> False
>>
>> Tracking bug
>>
>> https://bugs.chromium.org/p/chromium/issues/detail?id=1184863
>>
>> Launch bug
>>
>> https://bugs.chromium.org/p/chromium/issues/detail?id=1184862
>>
>> Estimated milestones
>>
>> OriginTrial desktop last
>>
>> 101 → 104
>>
>> OriginTrial desktop first
>>
>> 99
>>
>> OriginTrial android last
>>
>> 101 → 104
>>
>> OriginTrial android first
>>
>> 99
>>
>>
>>
>> Link to entry on the Chrome Platform Status
>>
>> https://chromestatus.com/feature/5646861215989760
>>
>> Links to previous Intent discussions
>>
>> Intent to Experiment:
>> https://groups.google.com/a/chromium.org/g/blink-dev/c/Q2wcqY2UyNs/m/rPePdX_NBwAJ
>>
>>
>> This intent message was generated by Chrome Plat

[blink-dev] Intent to Experiment: Viewport-height client hint

2022-04-06 Thread 'Max Curran' via blink-dev 
Contact emails

curran...@chromium.org, ryanst...@chromium.org

Explainer

https://github.com/WICG/responsive-image-client-hints/blob/master/Viewport-Height-Explainer.md

Specification

https://wicg.github.io/responsive-image-client-hints/#sec-ch-viewport-height

Summary

Currently, Responsive Image Client Hints provide a way for origins to
obtain the viewport’s width. However, no such attribute exists for viewport
height. We’ve observed that to optimize the loading of content that appears
in viewport, it is essential for the origins to adapt HTML response based
on viewport height.


Blink component

Blink>Loader


TAG review

https://github.com/w3ctag/design-reviews/issues/615

TAG review status

Issues addressed

Link to origin trial feedback summary

https://github.com/WICG/responsive-image-client-hints/issues

Risks

Interoperability and Compatibility

Gecko: No signal (https://github.com/mozilla/standards-positions/issues/79)

WebKit: Negative (
https://lists.webkit.org/pipermail/webkit-dev/2020-November/031576.html)
Likely to be neutral based on discussion in
https://github.com/mozilla/standards-positions/issues/79

Web developers: No signals

Other signals:

Activation

None


WebView Application Risks

Does this intent deprecate or change behavior of existing APIs, such that
it has potentially high risk for Android WebView-based applications?


Goals for experimentation

Client hints opt-ins from origins are session-sticky which makes it
difficult to experiment with using origin trials since origin trials
operate at document-level. We plan to run an A/B experiment using Chrome’s
field trial infrastructure. Our plan is to enable the feature for at most
1% users to collect metrics, and ship this feature only if it shows
performance improvement for origins that choose to use this feature.


Reason this experiment is being extended

Due to Chrome approvals taking longer than expected, and partners still
needing to implement how to use the client hint, we have not been able to
experiment yet. We would like to extend the origin trial from M101 to M104.

Ongoing technical constraints

Debuggability

N/A


Will this feature be supported on all six Blink platforms (Windows, Mac,
Linux, Chrome OS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests

?

Yes

Flag name

kViewportHeightClientHintHeader

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1184863

Launch bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1184862

Estimated milestones

OriginTrial desktop last

101 → 104

OriginTrial desktop first

99

OriginTrial android last

101 → 104

OriginTrial android first

99



Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5646861215989760

Links to previous Intent discussions

Intent to Experiment:
https://groups.google.com/a/chromium.org/g/blink-dev/c/Q2wcqY2UyNs/m/rPePdX_NBwAJ


This intent message was generated by Chrome Platform Status
.

-- 
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/CA%2BEneNNpr4CxoeqmHxgyTK3shuoN3f5T6hpfzkoT-zY2wR1SgA%40mail.gmail.com.

Re: [blink-dev] Intent to Experiment: Viewport-height client hint

2022-02-04 Thread 'Max Curran' via blink-dev 
We weren’t ready to start the experiments till now, and we are now planning 
on running experiments on M99-M101.

On Tuesday, August 24, 2021 at 2:41:25 AM UTC-7 yoav...@chromium.org wrote:

> Thanks for updating the thread! :)
>
> On Mon, Aug 23, 2021 at 10:01 PM 'Max Curran' via blink-dev <
> blin...@chromium.org> wrote:
>
>> This feature has slipped to M95.
>>
>> On Monday, August 2, 2021 at 8:21:55 AM UTC-7 Max Curran wrote:
>>
>>> Quick update: The experiment for the viewport-height client hint are not 
>>> active in M91-M93. The feature should be code complete in M94, and we plan 
>>> on start experimenting in that milestone.
>>>
>>> On Thursday, March 11, 2021 at 2:12:32 PM UTC-8 Chris Harrelson wrote:
>>>
>>>> Great!
>>>>
>>>> LGTM to experiment on M91 on canary/dev/beta.
>>>>
>>>> On Thu, Mar 11, 2021 at 2:03 PM Tarun Bansal  
>>>> wrote:
>>>>
>>>>> I think we should be able to get sufficient data on Canary/Dev/Beta 
>>>>> channels, but it's harder to predict for sure. The option to run first on 
>>>>> Canary/Dev/Beta channels and ping back this thread seems reasonable to 
>>>>> me. 
>>>>>
>>>>> On Thursday, March 11, 2021 at 2:00:27 PM UTC-8 Chris Harrelson wrote:
>>>>>
>>>> On Thu, Mar 11, 2021 at 1:36 PM Tarun Bansal  
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks Chris. Answers inline:
>>>>>>>
>>>>>>> > - Can you add a milestone range you'd like to experiment on? e.g. 
>>>>>>> M91-M93?
>>>>>>>
>>>>>>> We're hoping to start the experiment in M-91 (I updated this on 
>>>>>>> chromestatus as well).
>>>>>>>
>>>>>>> > - You're suggesting an A/B experiment rather than an Origin Trial, 
>>>>>>> since Origin Trials don't work at the networking layer; this makes 
>>>>>>> sense. 
>>>>>>> But since it's an A/B experiment, these headers will be exposed to all 
>>>>>>> sites in the A group. For this reason, would it suffice to test on the 
>>>>>>> Canary/Dev/Beta channels?
>>>>>>>
>>>>>>> The developers would need to opt-in to get those headers, and yes, 
>>>>>>> it would be possible for developers to opt-in, and get the headers from 
>>>>>>> the 
>>>>>>> users in group A. However, given the small size of group A, the opt-in 
>>>>>>> would succeed only <5% time on stable channel. I would hope developers 
>>>>>>> would not rely on it as long as we keep group A size small. 
>>>>>>>
>>>>>>
>>>>>> I agree that the risk is small, but even still it's better not to 
>>>>>> experiment with new APIs on the stable channel when possible. Do you 
>>>>>> think 
>>>>>> the audience sizes on other channels will be large enough to get a 
>>>>>> statistically significant result?
>>>>>>
>>>>>> Another option could be to run first on those channels, and if the 
>>>>>> results are not conclusive enough, ping this thread to request stable 
>>>>>> channel experimentation.
>>>>>>
>>>>>> On Thursday, March 11, 2021 at 1:13:13 PM UTC-8 Chris Harrelson wrote:
>>>>>>>
>>>>>> Hi,
>>>>>>>>
>>>>>>>> I have two questions:
>>>>>>>>
>>>>>>>> - Can you add a milestone range you'd like to experiment on? e.g. 
>>>>>>>> M91-M93?
>>>>>>>>
>>>>>>>> - You're suggesting an A/B experiment rather than an Origin Trial, 
>>>>>>>> since Origin Trials don't work at the networking layer; this makes 
>>>>>>>> sense. 
>>>>>>>> But since it's an A/B experiment, these headers will be exposed to all 
>>>>>>>> sites in the A group. For this reason, would it suffice to test on the 
>>>>>>>> Canary/Dev/Beta channels?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>  
>>>>>>>>
>>>>>>>>
>>>>>>>