Re: [blink-dev] Re: Intent to experiment - WebAssembly JavaScript Promise Integration (update)

2024-03-02 Thread Daniel Bratell 
The policy has changed a bit to accept a direct extension, without any 
breaks, where we previously didn't so it's possible the documentation 
you saw was outdated. The enforced break was to prevent burn-in that 
would make it painful to do suitable changes or drop an idea, but it 
seems that has not been a big problem so the process was tweaked.


/Daniel

On 2024-02-20 19:14, 'Francis McCabe' via blink-dev wrote:
I can live with that. However, the bureaucracy is overwhelming. To get 
an extension, the documentation I saw stated that I have to create a 
new OT.


On Tuesday, February 20, 2024 at 10:02:44 AM UTC-8 rby...@chromium.org 
wrote:


Sorry I missed this question! No, I did not notice that the entry
was for 10 milestones. Our policy


is a maximum of 6 milestones with 3-milestone renewals dependent
on showing significant progress towards standardization.Francis,
do you want to make this for M123-128 instead then plan to request
a renewal after that?

Rick

On Fri, Feb 2, 2024 at 9:09 PM Panos Astithas 
wrote:

Hey Rick,

This intent was updated to last between M123-M132 after
posting, but before approval. Since it's not clear whether you
looked at Chromestatus or the email thread, can you confirm
that your approval is indeed for these milestones?

Thanks,
Panos

On Thu, Jan 25, 2024 at 10:29 AM Mike Taylor
 wrote:

Yep - that is an official positive signal, thanks!

On 1/24/24 7:40 PM, Francis McCabe wrote:

Does this:

https://mozilla.github.io/standards-positions/#wasm-js-promise-integration
count as an official positive signal?

Francis

On Wed, Jan 24, 2024 at 3:09 AM Yoav Weiss (@Shopify)
 wrote:



On Friday, January 5, 2024 at 7:25:28 PM UTC+1
Francis McCabe wrote:

This is an update to the previous
intent-to-experiment (filled out a few more fields)

Contact emailsf...@chromium.org


Explainerhttps://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md




Specificationhttps://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md



Summary

Stack Switching denotes a technology that allows
programs to suspend and resume computation. This
is an active area that is part of the WebAssembly
standards track. See
https://github.com/WebAssembly/stack-switching

and
https://github.com/WebAssembly/meetings/tree/main/stack
.
This particular feature refers to the integration
between JavaScript Promises and stack switching.
This is described in more detail in

https://docs.google.com/document/d/16Us-pyte2-9DECJDfGm5tnUpfngJJOc8jbj54HMqE9Y/edit#





Blink componentBlink>JavaScript>WebAssembly



Search tagsstack switching
,
Promise
,
JSPI 

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


TAG review statusPending

Risks


Interoperability and Compatibility

This spec is backed by a standardization effort.
We do not plan to ship the JSPI until it has been
standardized by the W3C Wasm WG. However, post
standardization, we will depend on all browsers
implementing the standard.



/Gecko/:

Re: [blink-dev] Re: Intent to experiment - WebAssembly JavaScript Promise Integration (update)

2024-02-20 Thread 'Francis McCabe' via blink-dev 
I can live with that. However, the bureaucracy is overwhelming. To get an 
extension, the documentation I saw stated that I have to create a new OT. 

On Tuesday, February 20, 2024 at 10:02:44 AM UTC-8 rby...@chromium.org 
wrote:

> Sorry I missed this question! No, I did not notice that the entry was for 
> 10 milestones. Our policy 
> 
>  
> is a maximum of 6 milestones with 3-milestone renewals dependent on showing 
> significant progress towards standardization.Francis, do you want to make 
> this for M123-128 instead then plan to request a renewal after that?
>
> Rick
>
> On Fri, Feb 2, 2024 at 9:09 PM Panos Astithas  wrote:
>
>> Hey Rick,
>>
>> This intent was updated to last between M123-M132 after posting, but 
>> before approval. Since it's not clear whether you looked at Chromestatus or 
>> the email thread, can you confirm that your approval is indeed for these 
>> milestones?
>>
>> Thanks,
>> Panos
>>
>> On Thu, Jan 25, 2024 at 10:29 AM Mike Taylor  
>> wrote:
>>
>>> Yep - that is an official positive signal, thanks!
>>> On 1/24/24 7:40 PM, Francis McCabe wrote:
>>>
>>> Does this: 
>>> https://mozilla.github.io/standards-positions/#wasm-js-promise-integration 
>>> count as an official positive signal? 
>>>
>>> Francis
>>>
>>> On Wed, Jan 24, 2024 at 3:09 AM Yoav Weiss (@Shopify) <
>>> yoav...@chromium.org> wrote:
>>>


 On Friday, January 5, 2024 at 7:25:28 PM UTC+1 Francis McCabe wrote:

 This is an update to the previous intent-to-experiment (filled out a 
 few more fields) 

 Contact emailsf...@chromium.org

 Explainerhttps://github.com/WebAssembly/js-promise-
 integration/blob/main/proposals/js-promise-integration/Overview.md

 Specificationhttps://github.com/WebAssembly/js-promise-
 integration/blob/main/proposals/js-promise-integration/Overview.md

 Summary 

 Stack Switching denotes a technology that allows programs to suspend 
 and resume computation. This is an active area that is part of the 
 WebAssembly standards track. See https://github.com/
 WebAssembly/stack-switching and https://github.com/
 WebAssembly/meetings/tree/main/stack. This particular feature refers 
 to the integration between JavaScript Promises and stack switching. This 
 is 
 described in more detail in https://docs.google.com/
 document/d/16Us-pyte2-9DECJDfGm5tnUpfngJJOc8jbj54HMqE9Y/edit#


 Blink componentBlink>JavaScript>WebAssembly 
 

 Search tagsstack switching 
 , Promise 
 , JSPI 
 

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

 TAG review statusPending

 Risks 


 Interoperability and Compatibility 

 This spec is backed by a standardization effort. We do not plan to ship 
 the JSPI until it has been standardized by the W3C Wasm WG. However, post 
 standardization, we will depend on all browsers implementing the standard.


 *Gecko*: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1850627) 
 Mozilla have started their own imlementation


 That doesn't count as a positive signal. Please file for official 
 signals  (but that is not blocking for 
 this OT).
  


 *WebKit*: No signal

 *Web developers*: No signals

 *Other signals*:

 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 experimentationThis specification is getting close to 
 finalization. We would like feedback from a wider audience as to the 
 utility and convenience of using the API.

 In addition, we are interested in performance benchmarking in 
 production applications.

 Ongoing technical constraints 

 None.


 Debuggability 

 Developers can piggyback on existing DevTools support for Promises to 
 help with debugging JSPI applications. In particular the existing 
 mechanisms for constructing extended stack traces from so-called Promise 
 chains will also include stack traces from JSPI applications.


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

 Is this feature fully tested by web-platform-tests

Re: [blink-dev] Re: Intent to experiment - WebAssembly JavaScript Promise Integration (update)

2024-02-20 Thread Rick Byers 
Sorry I missed this question! No, I did not notice that the entry was for
10 milestones. Our policy

is a maximum of 6 milestones with 3-milestone renewals dependent on showing
significant progress towards standardization.Francis, do you want to make
this for M123-128 instead then plan to request a renewal after that?

Rick

On Fri, Feb 2, 2024 at 9:09 PM Panos Astithas  wrote:

> Hey Rick,
>
> This intent was updated to last between M123-M132 after posting, but
> before approval. Since it's not clear whether you looked at Chromestatus or
> the email thread, can you confirm that your approval is indeed for these
> milestones?
>
> Thanks,
> Panos
>
> On Thu, Jan 25, 2024 at 10:29 AM Mike Taylor 
> wrote:
>
>> Yep - that is an official positive signal, thanks!
>> On 1/24/24 7:40 PM, Francis McCabe wrote:
>>
>> Does this:
>> https://mozilla.github.io/standards-positions/#wasm-js-promise-integration
>> count as an official positive signal?
>>
>> Francis
>>
>> On Wed, Jan 24, 2024 at 3:09 AM Yoav Weiss (@Shopify) <
>> yoavwe...@chromium.org> wrote:
>>
>>>
>>>
>>> On Friday, January 5, 2024 at 7:25:28 PM UTC+1 Francis McCabe wrote:
>>>
>>> This is an update to the previous intent-to-experiment (filled out a few
>>> more fields)
>>>
>>> Contact emails...@chromium.org
>>>
>>> Explainerhttps://github.com/WebAssembly/js-promise-
>>> integration/blob/main/proposals/js-promise-integration/Overview.md
>>>
>>> Specificationhttps://github.com/WebAssembly/js-promise-
>>> integration/blob/main/proposals/js-promise-integration/Overview.md
>>>
>>> Summary
>>>
>>> Stack Switching denotes a technology that allows programs to suspend and
>>> resume computation. This is an active area that is part of the WebAssembly
>>> standards track. See https://github.com/WebAssembly/stack-switching and
>>> https://github.com/WebAssembly/meetings/tree/main/stack. This
>>> particular feature refers to the integration between JavaScript Promises
>>> and stack switching. This is described in more detail in
>>> https://docs.google.com/document/d/16Us-pyte2-
>>> 9DECJDfGm5tnUpfngJJOc8jbj54HMqE9Y/edit#
>>>
>>>
>>> Blink componentBlink>JavaScript>WebAssembly
>>> 
>>>
>>> Search tagsstack switching
>>> , Promise
>>> , JSPI
>>> 
>>>
>>> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/809
>>>
>>> TAG review statusPending
>>>
>>> Risks
>>>
>>>
>>> Interoperability and Compatibility
>>>
>>> This spec is backed by a standardization effort. We do not plan to ship
>>> the JSPI until it has been standardized by the W3C Wasm WG. However, post
>>> standardization, we will depend on all browsers implementing the standard.
>>>
>>>
>>> *Gecko*: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1850627)
>>> Mozilla have started their own imlementation
>>>
>>>
>>> That doesn't count as a positive signal. Please file for official
>>> signals  (but that is not blocking for
>>> this OT).
>>>
>>>
>>>
>>> *WebKit*: No signal
>>>
>>> *Web developers*: No signals
>>>
>>> *Other signals*:
>>>
>>> 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 experimentationThis specification is getting close to
>>> finalization. We would like feedback from a wider audience as to the
>>> utility and convenience of using the API.
>>>
>>> In addition, we are interested in performance benchmarking in production
>>> applications.
>>>
>>> Ongoing technical constraints
>>>
>>> None.
>>>
>>>
>>> Debuggability
>>>
>>> Developers can piggyback on existing DevTools support for Promises to
>>> help with debugging JSPI applications. In particular the existing
>>> mechanisms for constructing extended stack traces from so-called Promise
>>> chains will also include stack traces from JSPI applications.
>>>
>>>
>>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>>> Linux, ChromeOS, Android, and Android WebView)?Yes
>>>
>>> Is this feature fully tested by web-platform-tests
>>> 
>>> ?No
>>>
>>>
>>> I'm guessing it will be covered by tests, at least eventually?
>>>
>>>
>>>
>>>
>>> Flag name on chrome://flagsenable-experimental-
>>> webassembly-stack-switching
>>>
>>> Finch feature nameNone
>>>
>>> Non-finch justificationNone
>>>
>>> Requires code in //chrome?False
>>>
>>> Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=12191=
>>> owner%3Ame=2
>>>
>>> Estimated

Re: [blink-dev] Re: Intent to experiment - WebAssembly JavaScript Promise Integration (update)

2024-02-02 Thread 'Panos Astithas' via blink-dev 
Hey Rick,

This intent was updated to last between M123-M132 after posting, but before
approval. Since it's not clear whether you looked at Chromestatus or the
email thread, can you confirm that your approval is indeed for these
milestones?

Thanks,
Panos

On Thu, Jan 25, 2024 at 10:29 AM Mike Taylor  wrote:

> Yep - that is an official positive signal, thanks!
> On 1/24/24 7:40 PM, Francis McCabe wrote:
>
> Does this:
> https://mozilla.github.io/standards-positions/#wasm-js-promise-integration
> count as an official positive signal?
>
> Francis
>
> On Wed, Jan 24, 2024 at 3:09 AM Yoav Weiss (@Shopify) <
> yoavwe...@chromium.org> wrote:
>
>>
>>
>> On Friday, January 5, 2024 at 7:25:28 PM UTC+1 Francis McCabe wrote:
>>
>> This is an update to the previous intent-to-experiment (filled out a few
>> more fields)
>>
>> Contact emails...@chromium.org
>>
>> Explainerhttps://github.com/WebAssembly/js-promise-integration/blob/main/
>> proposals/js-promise-integration/Overview.md
>>
>> Specificationhttps://github.com/WebAssembly/js-promise-
>> integration/blob/main/proposals/js-promise-integration/Overview.md
>>
>> Summary
>>
>> Stack Switching denotes a technology that allows programs to suspend and
>> resume computation. This is an active area that is part of the WebAssembly
>> standards track. See https://github.com/WebAssembly/stack-switching and
>> https://github.com/WebAssembly/meetings/tree/main/stack. This particular
>> feature refers to the integration between JavaScript Promises and stack
>> switching. This is described in more detail in https://docs.google.com/
>> document/d/16Us-pyte2-9DECJDfGm5tnUpfngJJOc8jbj54HMqE9Y/edit#
>>
>>
>> Blink componentBlink>JavaScript>WebAssembly
>> 
>>
>> Search tagsstack switching
>> , Promise
>> , JSPI
>> 
>>
>> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/809
>>
>> TAG review statusPending
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>> This spec is backed by a standardization effort. We do not plan to ship
>> the JSPI until it has been standardized by the W3C Wasm WG. However, post
>> standardization, we will depend on all browsers implementing the standard.
>>
>>
>> *Gecko*: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1850627)
>> Mozilla have started their own imlementation
>>
>>
>> That doesn't count as a positive signal. Please file for official signals
>>  (but that is not blocking for this OT).
>>
>>
>>
>> *WebKit*: No signal
>>
>> *Web developers*: No signals
>>
>> *Other signals*:
>>
>> 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 experimentationThis specification is getting close to
>> finalization. We would like feedback from a wider audience as to the
>> utility and convenience of using the API.
>>
>> In addition, we are interested in performance benchmarking in production
>> applications.
>>
>> Ongoing technical constraints
>>
>> None.
>>
>>
>> Debuggability
>>
>> Developers can piggyback on existing DevTools support for Promises to
>> help with debugging JSPI applications. In particular the existing
>> mechanisms for constructing extended stack traces from so-called Promise
>> chains will also include stack traces from JSPI applications.
>>
>>
>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>> Linux, ChromeOS, Android, and Android WebView)?Yes
>>
>> Is this feature fully tested by web-platform-tests
>> 
>> ?No
>>
>>
>> I'm guessing it will be covered by tests, at least eventually?
>>
>>
>>
>>
>> Flag name on chrome://flagsenable-experimental-
>> webassembly-stack-switching
>>
>> Finch feature nameNone
>>
>> Non-finch justificationNone
>>
>> Requires code in //chrome?False
>>
>> Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=12191=
>> owner%3Ame=2
>>
>> Estimated milestonesOriginTrial desktop last130OriginTrial desktop first
>> 122OriginTrial Android last130OriginTrial Android first122OriginTrial
>> webView last130OriginTrial webView first122
>>
>> Link to entry on the Chrome Platform Statushttps://chromestatus.com/
>> feature/5674874568704000
>>
>> Links to previous Intent discussionsIntent to prototype: https://groups.
>> google.com/a/chromium.org/d/msgid/blink-dev/
>> CAAdKk6BGFseZ6pBO2qEW_xeovVw1_guVq26rcNM1nWY442Y5Ng%40mail.gmail.com Intent
>> to Experiment: https://groups.google.com/a/chromium.org/d/
>> msgid/blink-dev/CAE65UWD8e57Bd5x3nr63M3QcdPo6TKom%2BVZT%3DvO2Uo4x6th_kA%
>> 40mail.gmail.com
>>
>>
>> This intent message was generated by Chrome Platform Status
>>

Re: [blink-dev] Re: Intent to experiment - WebAssembly JavaScript Promise Integration (update)

2024-01-25 Thread Mike Taylor 

Yep - that is an official positive signal, thanks!

On 1/24/24 7:40 PM, Francis McCabe wrote:
Does this: 
https://mozilla.github.io/standards-positions/#wasm-js-promise-integration 
count as an official positive signal?


Francis

On Wed, Jan 24, 2024 at 3:09 AM Yoav Weiss (@Shopify) 
 wrote:




On Friday, January 5, 2024 at 7:25:28 PM UTC+1 Francis McCabe wrote:

This is an update to the previous intent-to-experiment (filled
out a few more fields)

Contact emails...@chromium.org


Explainerhttps://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md




Specificationhttps://github.com/WebAssembly/js-promise-integration/blob/main/proposals/js-promise-integration/Overview.md



Summary

Stack Switching denotes a technology that allows programs to
suspend and resume computation. This is an active area that is
part of the WebAssembly standards track. See
https://github.com/WebAssembly/stack-switching
 and
https://github.com/WebAssembly/meetings/tree/main/stack
.
This particular feature refers to the integration between
JavaScript Promises and stack switching. This is described in
more detail in

https://docs.google.com/document/d/16Us-pyte2-9DECJDfGm5tnUpfngJJOc8jbj54HMqE9Y/edit#





Blink componentBlink>JavaScript>WebAssembly



Search tagsstack switching
,
Promise , JSPI


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


TAG review statusPending

Risks


Interoperability and Compatibility

This spec is backed by a standardization effort. We do not
plan to ship the JSPI until it has been standardized by the
W3C Wasm WG. However, post standardization, we will depend on
all browsers implementing the standard.



/Gecko/: Positive
(https://bugzilla.mozilla.org/show_bug.cgi?id=1850627
)
Mozilla have started their own imlementation


That doesn't count as a positive signal. Please file for official
signals  (but that is not blocking
for this OT).


/WebKit/: No signal

/Web developers/: No signals

/Other signals/:

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 experimentationThis specification is getting close
to finalization. We would like feedback from a wider audience
as to the utility and convenience of using the API.

In addition, we are interested in performance benchmarking in
production applications.

Ongoing technical constraints

None.



Debuggability

Developers can piggyback on existing DevTools support for
Promises to help with debugging JSPI applications. In
particular the existing mechanisms for constructing extended
stack traces from so-called Promise chains will also include
stack traces from JSPI applications.



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

Is this feature fully tested by web-platform-tests

?No


I'm guessing it will be covered by tests, at least eventually?



Flag name on
chrome://flagsenable-experimental-webassembly-stack-switching

Finch feature nameNone

Non-finch justificationNone

Requires code in //chrome?False

Tracking

bughttps://bugs.chromium.org/p/v8/issues/detail?id=12191=owner%3Ame=2



Estimated milestonesOriginTrial desktop last130OriginTrial
desktop first122OriginTrial Android last130OriginTrial Android
first122OriginTrial webView

Re: [blink-dev] Re: Intent to experiment - WebAssembly JavaScript Promise Integration (update)

2024-01-24 Thread Rick Byers 
My only OT-blocking concern in the original thread was the "developers: no
signals". But that was answered there
.
Yoav, I think your questions are not OT-blocking, right?

LGTM to experiment.

On Wed, Jan 24, 2024 at 6:09 AM Yoav Weiss (@Shopify) <
yoavwe...@chromium.org> wrote:

>
>
> On Friday, January 5, 2024 at 7:25:28 PM UTC+1 Francis McCabe wrote:
>
> This is an update to the previous intent-to-experiment (filled out a few
> more fields)
>
> Contact emails...@chromium.org
>
> Explainerhttps://github.com/WebAssembly/js-promise-integration/blob/main/
> proposals/js-promise-integration/Overview.md
>
> Specificationhttps://github.com/WebAssembly/js-promise-
> integration/blob/main/proposals/js-promise-integration/Overview.md
>
> Summary
>
> Stack Switching denotes a technology that allows programs to suspend and
> resume computation. This is an active area that is part of the WebAssembly
> standards track. See https://github.com/WebAssembly/stack-switching and
> https://github.com/WebAssembly/meetings/tree/main/stack. This particular
> feature refers to the integration between JavaScript Promises and stack
> switching. This is described in more detail in https://docs.google.com/
> document/d/16Us-pyte2-9DECJDfGm5tnUpfngJJOc8jbj54HMqE9Y/edit#
>
>
> Blink componentBlink>JavaScript>WebAssembly
> 
>
> Search tagsstack switching
> , Promise
> , JSPI
> 
>
> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/809
>
> TAG review statusPending
>
> Risks
>
>
> Interoperability and Compatibility
>
> This spec is backed by a standardization effort. We do not plan to ship
> the JSPI until it has been standardized by the W3C Wasm WG. However, post
> standardization, we will depend on all browsers implementing the standard.
>
>
> *Gecko*: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1850627)
> Mozilla have started their own imlementation
>
>
> That doesn't count as a positive signal. Please file for official signals
>  (but that is not blocking for this OT).
>
>
>
> *WebKit*: No signal
>
> *Web developers*: No signals
>
> *Other signals*:
>
> 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
>
> This specification is getting close to finalization. We would like
> feedback from a wider audience as to the utility and convenience of using
> the API.
>
> In addition, we are interested in performance benchmarking in production
> applications.
>
> Ongoing technical constraints
>
> None.
>
>
> Debuggability
>
> Developers can piggyback on existing DevTools support for Promises to help
> with debugging JSPI applications. In particular the existing mechanisms for
> constructing extended stack traces from so-called Promise chains will also
> include stack traces from JSPI applications.
>
>
> Will this feature be supported on all six Blink platforms (Windows, Mac,
> Linux, ChromeOS, Android, and Android WebView)?Yes
>
> Is this feature fully tested by web-platform-tests
> 
> ?No
>
>
> I'm guessing it will be covered by tests, at least eventually?
>
>
>
>
> Flag name on chrome://flagsenable-experimental-webassembly-stack-switching
>
> Finch feature nameNone
>
> Non-finch justificationNone
>
> Requires code in //chrome?False
>
> Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=12191=
> owner%3Ame=2
>
> Estimated milestonesOriginTrial desktop last130OriginTrial desktop first
> 122OriginTrial Android last130OriginTrial Android first122OriginTrial
> webView last130OriginTrial webView first122
>
> Link to entry on the Chrome Platform Statushttps://chromestatus.com/
> feature/5674874568704000
>
> Links to previous Intent discussionsIntent to prototype: https://groups.
> google.com/a/chromium.org/d/msgid/blink-dev/CAAdKk6BGFseZ6pBO2qEW_xeovVw1_
> guVq26rcNM1nWY442Y5Ng%40mail.gmail.com Intent to Experiment:
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/
> CAE65UWD8e57Bd5x3nr63M3QcdPo6TKom%2BVZT%3DvO2Uo4x6th_kA%40mail.gmail.com
>
>
> 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
>