Re: [blink-dev] Intent to Extend Experiment: Conditional Focus

[Yoav Weiss]

LGTM to extend experimentation till 111 inclusive. Thanks for working on
standardizing this, and landing the PRs.

On Wed, Sep 21, 2022 at 9:50 AM 'Elad Alon' via blink-dev <
blink-dev@chromium.org> wrote:

> Hi Blink owners,
>
> We'd like to extend the Conditional Focus experiment again. It is
> currently running m102-m108, and we'd like to extend by 3 additional
> milestones, making it m102-m111 (inclusive).
>
> There has been significant progress in discussions lately, and we have a
> new API shape which has rough consensus in the WG. However, it will take
> time to fully finalize that shape's fine details, align the implementation
> and ship. During this time, we'd like to (1) show consideration to our
> partners and (2) keep their feedback coming in. The latter is especially
> true given that a major partner is about to start experimenting on real
> users, which will provide even more useful feedback than thus far (when
> they only prototyped and tested internally).
>
> Contact emailselada...@chromium.org
>
> Explainerhttps://github.com/WICG/conditional-focus/blob/main/README.md
>
> Specificationhttps://wicg.github.io/conditional-focus
>
> Design docs
>
> https://docs.google.com/document/d/1LHJRt-ry9hwzFTbPxKrmD0VvtEFEU6lvqsD7k6wwGKM
>
> Summary
>
> Extend the getDisplayMedia() APIs to ensure that tab-capture and
> window-capture return a new subclass of MediaStreamTrack called
> FocusableMediaStreamTrack. This new subclass exposes the focus() method.
> This new method allows Web-applications, when capture starts, to decide
> whether the captured tab/window should be immediately focused, or whether
> the capturing tab+window should remain the focused one.
>
>
> Blink componentBlink
> 
>
> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/679
>
> TAG review statusPending
>
> Risks
>
>
> Interoperability and Compatibility
>
>
>
> *Gecko*: No signal
>
> *WebKit*: No signal
>
> *Web developers*: No signals
>
> *Other signals*:
>
> Ergonomics
>
> N/A
>
>
> Activation
>
> Not challenging - just feature-detect: // Pre-existing functionality:
> const mediaStream = await navigator.mediaDevices.getDisplayMedia(); const
> [track] = mediaStream.getVideoTracks(); // New functionality behind
> feature-detection: if (!!track.focus) { track.focus(...); }
>
>
> Security
>
> See design-doc.
>
> Reason this experiment is being extended
>
> The WebRTC WG has reached rough consensus on Conditional Focus. The
> conclusions are summarized in these two threads (190
> , 230
> ), and most
> recently in this comment
> .
> It is now on me to produce a PR, get it through review, and then align the
> Chromium implementation with it.
>
> It's not likely that all of this will be done before m109 branches. I
> therefore request that the OT be extended by 3 additional milestones (up to
> and including m111). This will allow us to finalize Conditional Focus work
> without penalizing the partners that have been kind enough to participate
> in the trial and provide feedback. It would also help that we'll have more
> time to get feedback from a major partner, who has only provided feedback
> based on prototypes thus far, but who will soon have feedback based on an
> experiment with real users.
>
> We are therefore requesting extension by 3 milestones, making the
> experiment run for m102-m111 (inclusive).
>
> Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, Chrome OS, Android, and Android WebView)?
>
> Supported on all Desktop platforms, but not on any mobile platforms.
>
>
> Is this feature fully tested by web-platform-tests
> 
> ?No
>
> Flag nameConditionalFocus
>
> Tracking bug
> https://bugs.chromium.org/p/chromium/issues/detail?id=1215480
>
> Launch bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1214483
>
> Estimated milestones
> OriginTrial desktop last 108 (but extension to 111 hereby requested)
> OriginTrial desktop first 102
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5646614535340032
>
> Links to previous Intent discussionsIntent to prototype:
> https://groups.google.com/a/chromium.org/g/blink-dev/c/lbuqOGx07xY
> Intent to Experiment:
> https://groups.google.com/a/chromium.org/g/blink-dev/c/I4RE2pbocTg
> Intent to Extend Experiment:
> https://groups.google.com/a/chromium.org/g/blink-dev/c/CLmSojRQHoc
>
> --
> 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.

[blink-dev] Intent to Extend Experiment: Conditional Focus

['Elad Alon' via blink-dev]

Hi Blink owners,

We'd like to extend the Conditional Focus experiment again. It is currently
running m102-m108, and we'd like to extend by 3 additional milestones,
making it m102-m111 (inclusive).

There has been significant progress in discussions lately, and we have a
new API shape which has rough consensus in the WG. However, it will take
time to fully finalize that shape's fine details, align the implementation
and ship. During this time, we'd like to (1) show consideration to our
partners and (2) keep their feedback coming in. The latter is especially
true given that a major partner is about to start experimenting on real
users, which will provide even more useful feedback than thus far (when
they only prototyped and tested internally).

Contact emailselada...@chromium.org

Explainerhttps://github.com/WICG/conditional-focus/blob/main/README.md

Specificationhttps://wicg.github.io/conditional-focus

Design docs
https://docs.google.com/document/d/1LHJRt-ry9hwzFTbPxKrmD0VvtEFEU6lvqsD7k6wwGKM

Summary

Extend the getDisplayMedia() APIs to ensure that tab-capture and
window-capture return a new subclass of MediaStreamTrack called
FocusableMediaStreamTrack. This new subclass exposes the focus() method.
This new method allows Web-applications, when capture starts, to decide
whether the captured tab/window should be immediately focused, or whether
the capturing tab+window should remain the focused one.


Blink componentBlink


TAG reviewhttps://github.com/w3ctag/design-reviews/issues/679

TAG review statusPending

Risks


Interoperability and Compatibility



*Gecko*: No signal

*WebKit*: No signal

*Web developers*: No signals

*Other signals*:

Ergonomics

N/A


Activation

Not challenging - just feature-detect: // Pre-existing functionality: const
mediaStream = await navigator.mediaDevices.getDisplayMedia(); const [track]
= mediaStream.getVideoTracks(); // New functionality behind
feature-detection: if (!!track.focus) { track.focus(...); }


Security

See design-doc.

Reason this experiment is being extended

The WebRTC WG has reached rough consensus on Conditional Focus. The
conclusions are summarized in these two threads (190
, 230
), and most
recently in this comment
.
It is now on me to produce a PR, get it through review, and then align the
Chromium implementation with it.

It's not likely that all of this will be done before m109 branches. I
therefore request that the OT be extended by 3 additional milestones (up to
and including m111). This will allow us to finalize Conditional Focus work
without penalizing the partners that have been kind enough to participate
in the trial and provide feedback. It would also help that we'll have more
time to get feedback from a major partner, who has only provided feedback
based on prototypes thus far, but who will soon have feedback based on an
experiment with real users.

We are therefore requesting extension by 3 milestones, making the
experiment run for m102-m111 (inclusive).

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

Supported on all Desktop platforms, but not on any mobile platforms.


Is this feature fully tested by web-platform-tests

?No

Flag nameConditionalFocus

Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1215480

Launch bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1214483

Estimated milestones
OriginTrial desktop last 108 (but extension to 111 hereby requested)
OriginTrial desktop first 102

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5646614535340032

Links to previous Intent discussionsIntent to prototype:
https://groups.google.com/a/chromium.org/g/blink-dev/c/lbuqOGx07xY
Intent to Experiment:
https://groups.google.com/a/chromium.org/g/blink-dev/c/I4RE2pbocTg
Intent to Extend Experiment:
https://groups.google.com/a/chromium.org/g/blink-dev/c/CLmSojRQHoc

-- 
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/CAMO6jDO63PGOoMhJTfV1pHsPuV9VmoCVdqyx%2BpTzCtyTUYBV8w%40mail.gmail.com.

Re: [blink-dev] Intent to Extend Experiment: Conditional Focus

[Yoav Weiss]

Can you send a separate extension intent for this? Thanks! :)

On Sat, Sep 17, 2022 at 2:04 AM 'Elad Alon' via blink-dev <
blink-dev@chromium.org> wrote:

> Hello Blink owners. The WebRTC WG has reached rough consensus on
> Conditional Focus. The conclusions are summarized in these two threads (
> 190 , 230
> ), and most
> recently in this comment
> .
> It is now on me to produce a PR, get it through review, and then align the
> Chromium implementation with it. It's not likely that all of this will be
> done before m109 branches. I therefore request that the OT be extended by 3
> additional milestones (up to and including m111). This will allow us to
> finalize Conditional Focus work without penalizing the partners that have
> been kind enough to participate in the trial and provide feedback. It would
> also help that we'll have more time to get feedback.
>
> On Friday, August 19, 2022 at 7:35:32 AM UTC-7 mike...@chromium.org wrote:
>
>> LGTM to extend to M108 inclusive.
>>
>> On 8/18/22 4:33 PM, 'Elad Alon' via blink-dev wrote:
>>
>> Hi Blink owners,
>>
>> We'd like to extend the Conditional Focus experiment. It is currently
>> running m102-m105, and we'd like to extend by 3 additional milestones,
>> making it m102-m108 (inclusive).
>>
>> Contact emails elad...@chromium.org
>>
>> Explainer https://github.com/WICG/conditional-focus/blob/main/README.md
>>
>> Specification https://wicg.github.io/conditional-focus
>>
>> Design docs
>>
>> https://docs.google.com/document/d/1LHJRt-ry9hwzFTbPxKrmD0VvtEFEU6lvqsD7k6wwGKM
>>
>> Summary
>>
>> Extend the getDisplayMedia() APIs to ensure that tab-capture and
>> window-capture return a new subclass of MediaStreamTrack called
>> FocusableMediaStreamTrack. This new subclass exposes the focus() method.
>> This new method allows Web-applications, when capture starts, to decide
>> whether the captured tab/window should be immediately focused, or whether
>> the capturing tab+window should remain the focused one.
>>
>>
>> Blink component Blink
>> 
>>
>> TAG review https://github.com/w3ctag/design-reviews/issues/679
>>
>> TAG review status Pending
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>> *Gecko*: No signal
>>
>> *WebKit*: No signal
>>
>> *Web developers*: No signals
>>
>> *Other signals*:
>>
>> Ergonomics
>>
>> N/A
>>
>>
>> Activation
>>
>> Not challenging - just feature-detect: // Pre-existing functionality:
>> const mediaStream = await navigator.mediaDevices.getDisplayMedia(); const
>> [track] = mediaStream.getVideoTracks(); // New functionality behind
>> feature-detection: if (!!track.focus) { track.focus(...); }
>>
>>
>> Security
>>
>> See design-doc.
>>
>> Reason this experiment is being extended 0. Some relevant background:
>> Originally, this feature ended up ready and in Origin Trial quite some time
>> before our partners were ready to take advantage and participate in the
>> experiment. The OT was therefore *shifted* and *restarted* multiple
>> times, eventually landing on the range of m102-m105. Our partners are now
>> ready and have started rolling out code taking advantage of this feature -
>> so far internally within their organization, and soon to the general
>> public.
>> 1. More time is required for our partners' deliberate rollout to reach
>> more users, allowing these partners to provide more accurate, battle-tested
>> feedback.
>> 2. Mozilla and Apple have both engaged positively with the proposal (see
>> here ).
>> Mozilla has made a proposal
>> 
>> for a general change to getDisplayMedia(), and suggested that the API shape
>> of Conditional Focus should be altered to fit that new shape. The added
>> complexity of tying Conditional Focus to adjacent API changes prolongs the
>> time to finalize Conditional Focus. While this is ongoing, we should keep
>> supporting partners who have invested engineering time in this OT.
>>
>> We are therefore requesting extension by 3 milestones, making the
>> experiment run for m102-m108 (inclusive).
>>
>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>> Linux, Chrome OS, Android, and Android WebView)?
>>
>> Supported on all Desktop platforms, but not on any mobile platforms.
>>
>>
>> Is this feature fully tested by web-platform-tests
>> 
>> ? No
>>
>> Flag name ConditionalFocus
>>
>> Tracking bug
>> https://bugs.chromium.org/p/chromium/issues/detail?id=1215480
>>
>> Launch bug https://bugs.chromium.org/p/chromium/issues/detail?id=1214483
>>
>> E

Re: [blink-dev] Intent to Extend Experiment: Conditional Focus

['Elad Alon' via blink-dev]

Hello Blink owners. The WebRTC WG has reached rough consensus on 
Conditional Focus. The conclusions are summarized in these two threads (190 
, 230 
), and most 
recently in this comment 
.
 
It is now on me to produce a PR, get it through review, and then align the 
Chromium implementation with it. It's not likely that all of this will be 
done before m109 branches. I therefore request that the OT be extended by 3 
additional milestones (up to and including m111). This will allow us to 
finalize Conditional Focus work without penalizing the partners that have 
been kind enough to participate in the trial and provide feedback. It would 
also help that we'll have more time to get feedback.

On Friday, August 19, 2022 at 7:35:32 AM UTC-7 mike...@chromium.org wrote:

> LGTM to extend to M108 inclusive.
>
> On 8/18/22 4:33 PM, 'Elad Alon' via blink-dev wrote:
>
> Hi Blink owners, 
>
> We'd like to extend the Conditional Focus experiment. It is currently 
> running m102-m105, and we'd like to extend by 3 additional milestones, 
> making it m102-m108 (inclusive).
>
> Contact emails elad...@chromium.org
>
> Explainer https://github.com/WICG/conditional-focus/blob/main/README.md
>
> Specification https://wicg.github.io/conditional-focus
>
> Design docs 
>
> https://docs.google.com/document/d/1LHJRt-ry9hwzFTbPxKrmD0VvtEFEU6lvqsD7k6wwGKM
>
> Summary 
>
> Extend the getDisplayMedia() APIs to ensure that tab-capture and 
> window-capture return a new subclass of MediaStreamTrack called 
> FocusableMediaStreamTrack. This new subclass exposes the focus() method. 
> This new method allows Web-applications, when capture starts, to decide 
> whether the captured tab/window should be immediately focused, or whether 
> the capturing tab+window should remain the focused one.
>
>
> Blink component Blink 
> 
>
> TAG review https://github.com/w3ctag/design-reviews/issues/679
>
> TAG review status Pending
>
> Risks 
>
>
> Interoperability and Compatibility 
>
> *Gecko*: No signal
>
> *WebKit*: No signal
>
> *Web developers*: No signals
>
> *Other signals*:
>
> Ergonomics 
>
> N/A
>
>
> Activation 
>
> Not challenging - just feature-detect: // Pre-existing functionality: 
> const mediaStream = await navigator.mediaDevices.getDisplayMedia(); const 
> [track] = mediaStream.getVideoTracks(); // New functionality behind 
> feature-detection: if (!!track.focus) { track.focus(...); }
>
>
> Security 
>
> See design-doc.
>
> Reason this experiment is being extended 0. Some relevant background: 
> Originally, this feature ended up ready and in Origin Trial quite some time 
> before our partners were ready to take advantage and participate in the 
> experiment. The OT was therefore *shifted* and *restarted* multiple 
> times, eventually landing on the range of m102-m105. Our partners are now 
> ready and have started rolling out code taking advantage of this feature - 
> so far internally within their organization, and soon to the general 
> public. 
> 1. More time is required for our partners' deliberate rollout to reach 
> more users, allowing these partners to provide more accurate, battle-tested 
> feedback.
> 2. Mozilla and Apple have both engaged positively with the proposal (see 
> here ). 
> Mozilla has made a proposal 
> 
>  
> for a general change to getDisplayMedia(), and suggested that the API shape 
> of Conditional Focus should be altered to fit that new shape. The added 
> complexity of tying Conditional Focus to adjacent API changes prolongs the 
> time to finalize Conditional Focus. While this is ongoing, we should keep 
> supporting partners who have invested engineering time in this OT.
>
> We are therefore requesting extension by 3 milestones, making the 
> experiment run for m102-m108 (inclusive).
>
> Will this feature be supported on all six Blink platforms (Windows, Mac, 
> Linux, Chrome OS, Android, and Android WebView)? 
>
> Supported on all Desktop platforms, but not on any mobile platforms.
>
>
> Is this feature fully tested by web-platform-tests 
> 
> ? No
>
> Flag name ConditionalFocus
>
> Tracking bug
> https://bugs.chromium.org/p/chromium/issues/detail?id=1215480
>
> Launch bug https://bugs.chromium.org/p/chromium/issues/detail?id=1214483
>
> Estimated milestones 
> OriginTrial desktop last 105 (but extension to 108 hereby requested) 
> OriginTrial desktop first 102 
>
> Link to entry on the Chrome Platform Status 
> https://chromestatus.com/feature/5646614535340032
>
> Links t

Re: [blink-dev] Intent to Extend Experiment: Conditional Focus

[Mike Taylor]

LGTM to extend to M108 inclusive.

On 8/18/22 4:33 PM, 'Elad Alon' via blink-dev wrote:



Hi Blink owners,


We'd like to extend the Conditional Focus experiment. It is currently 
running m102-m105, and we'd like to extend by 3 additional milestones, 
making it m102-m108 (inclusive).




Contact emails

elada...@chromium.org


Explainer

https://github.com/WICG/conditional-focus/blob/main/README.md


Specification

https://wicg.github.io/conditional-focus


Design docs


https://docs.google.com/document/d/1LHJRt-ry9hwzFTbPxKrmD0VvtEFEU6lvqsD7k6wwGKM


Summary

Extend the getDisplayMedia() APIs to ensure that tab-capture and 
window-capture return a new subclass of MediaStreamTrack called 
FocusableMediaStreamTrack. This new subclass exposes the focus() 
method. This new method allows Web-applications, when capture starts, 
to decide whether the captured tab/window should be immediately 
focused, or whether the capturing tab+window should remain the focused 
one.




Blink component

Blink 


TAG review

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


TAG review status

Pending


Risks



Interoperability and Compatibility



/Gecko/: No signal

/WebKit/: No signal

/Web developers/: No signals

/Other signals/:


Ergonomics

N/A



Activation

Not challenging - just feature-detect: // Pre-existing functionality: 
const mediaStream = await navigator.mediaDevices.getDisplayMedia(); 
const [track] = mediaStream.getVideoTracks(); // New functionality 
behind feature-detection: if (!!track.focus) { track.focus(...); }




Security

See design-doc.


Reason this experiment is being extended

0. Some relevant background: Originally, this feature ended up ready 
and in Origin Trial quite some time before our partners were ready to 
take advantage and participate in the experiment. The OT was therefore 
_shifted_ and _restarted_ multiple times, eventually landing on the 
range of m102-m105. Our partners are now ready and have started 
rolling out code taking advantage of this feature - so far internally 
within their organization, and soon to the general public.
1. More time is required for our partners' deliberate rollout to reach 
more users, allowing these partners to provide more accurate, 
battle-tested feedback.
2. Mozilla and Apple have both engaged positively with the proposal 
(see here 
). 
Mozilla has made a proposal 
 
for a general change to getDisplayMedia(), and suggested that the API 
shape of Conditional Focus should be altered to fit that new shape. 
The added complexity of tying Conditional Focus to adjacent API 
changes prolongs the time to finalize Conditional Focus. While this is 
ongoing, we should keep supporting partners who have invested 
engineering time in this OT.


We are therefore requesting extension by 3 milestones, making the 
experiment run for m102-m108 (inclusive).




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

Supported on all Desktop platforms, but not on any mobile platforms.



Is this feature fully tested by web-platform-tests

?

No


Flag name

ConditionalFocus


Tracking bug

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


Launch bug

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


Estimated milestones

OriginTrial desktop last105 (but extension to 108 hereby requested)
OriginTrial desktop first   102



Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5646614535340032


Links to previous Intent discussions

Intent to prototype: 
https://groups.google.com/a/chromium.org/g/blink-dev/c/lbuqOGx07xY
Intent to Experiment: 
https://groups.google.com/a/chromium.org/g/blink-dev/c/I4RE2pbocTg



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/CAMO6jDPC5EYjk1k%2B6_46erSvGNRYMkWk1Uxo4xGpouO4ROFDmQ%40mail.gmail.com 
.


--
You received this message because you are subscribed to the G

[blink-dev] Intent to Extend Experiment: Conditional Focus

['Elad Alon' via blink-dev]

Hi Blink owners,

We'd like to extend the Conditional Focus experiment. It is currently
running m102-m105, and we'd like to extend by 3 additional milestones,
making it m102-m108 (inclusive).

Contact emailselada...@chromium.org

Explainerhttps://github.com/WICG/conditional-focus/blob/main/README.md

Specificationhttps://wicg.github.io/conditional-focus

Design docs
https://docs.google.com/document/d/1LHJRt-ry9hwzFTbPxKrmD0VvtEFEU6lvqsD7k6wwGKM

Summary

Extend the getDisplayMedia() APIs to ensure that tab-capture and
window-capture return a new subclass of MediaStreamTrack called
FocusableMediaStreamTrack. This new subclass exposes the focus() method.
This new method allows Web-applications, when capture starts, to decide
whether the captured tab/window should be immediately focused, or whether
the capturing tab+window should remain the focused one.


Blink componentBlink


TAG reviewhttps://github.com/w3ctag/design-reviews/issues/679

TAG review statusPending

Risks


Interoperability and Compatibility



*Gecko*: No signal

*WebKit*: No signal

*Web developers*: No signals

*Other signals*:

Ergonomics

N/A


Activation

Not challenging - just feature-detect: // Pre-existing functionality: const
mediaStream = await navigator.mediaDevices.getDisplayMedia(); const [track]
= mediaStream.getVideoTracks(); // New functionality behind
feature-detection: if (!!track.focus) { track.focus(...); }


Security

See design-doc.

Reason this experiment is being extended

0. Some relevant background: Originally, this feature ended up ready and in
Origin Trial quite some time before our partners were ready to take
advantage and participate in the experiment. The OT was therefore *shifted* and
*restarted* multiple times, eventually landing on the range of m102-m105.
Our partners are now ready and have started rolling out code taking
advantage of this feature - so far internally within their organization,
and soon to the general public.
1. More time is required for our partners' deliberate rollout to reach more
users, allowing these partners to provide more accurate, battle-tested
feedback.
2. Mozilla and Apple have both engaged positively with the proposal (see
here ).
Mozilla has made a proposal

for a general change to getDisplayMedia(), and suggested that the API shape
of Conditional Focus should be altered to fit that new shape. The added
complexity of tying Conditional Focus to adjacent API changes prolongs the
time to finalize Conditional Focus. While this is ongoing, we should keep
supporting partners who have invested engineering time in this OT.

We are therefore requesting extension by 3 milestones, making the
experiment run for m102-m108 (inclusive).

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

Supported on all Desktop platforms, but not on any mobile platforms.


Is this feature fully tested by web-platform-tests

?No

Flag nameConditionalFocus

Tracking bug
https://bugs.chromium.org/p/chromium/issues/detail?id=1215480

Launch bughttps://bugs.chromium.org/p/chromium/issues/detail?id=1214483

Estimated milestones
OriginTrial desktop last 105 (but extension to 108 hereby requested)
OriginTrial desktop first 102

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5646614535340032

Links to previous Intent discussionsIntent to prototype:
https://groups.google.com/a/chromium.org/g/blink-dev/c/lbuqOGx07xY
Intent to Experiment:
https://groups.google.com/a/chromium.org/g/blink-dev/c/I4RE2pbocTg


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/CAMO6jDPC5EYjk1k%2B6_46erSvGNRYMkWk1Uxo4xGpouO4ROFDmQ%40mail.gmail.com.