[blink-dev] Intent to Ship: WebAssembly Multi-Memory

2023-10-17 Thread Clemens Backes 
Contact emailscleme...@google.com

ExplainerWe are ready for shipping the Multi-Memory proposal for
WebAssembly, which recently moved to phase 4 according to the WebAssembly
W3C process.

Specification
https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md

Design docs
https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md

Summary

Add support for more than one memory per WebAssembly module as specified in
the WebAssembly Multi-Memory proposal:
https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md

Blink componentBlink>JavaScript>WebAssembly


Search tagsWasm , WebAssembly
, Multi-Memory


TAG reviewNot required as per: https://v8.dev/docs/feature-launch-process.
TAG review statusNot applicable

Risks

Interoperability and Compatibility

None


*Gecko*: Positive

*WebKit*: Positive

*Web developers*: Strongly positive (
https://github.com/WebAssembly/proposals)

*Other signals*: This was voted to phase 4 (standardization) at the October
2023 WebAssembly Community Group meeting. 38 of 43 votes were "strongly
for".

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?

None


Debuggability

All memories are inspectable from DevTools, just like the first memory.

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

?

The WebAssembly proposal comes with all relevant tests; we pass them.

Flag name on chrome://flagsenable-experimental-webassembly-features

Finch feature nameNone

Non-finch justificationNone

Requires code in //chrome?False

Tracking bughttps://crbug.com/v8/13918

Estimated milestones
Shipping on desktop 120
DevTrial on desktop 117
Shipping on Android 120
DevTrial on Android 117
Shipping on WebView 120
Shipping on WebView 120
DevTrial on iOS 117

Anticipated spec changes

None.

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


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/CAGO%3DqhA9xWgZXnGbC%2BYQ9XqJUmLwgxsyggKa9mGhsY%3DOXpzcsg%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: WebAssembly Multi-Memory

2023-10-17 Thread Alex Russell 
It's unclear why the TAG is not being informed or consulted. This has deep
architectural implications for DOM integration and I'd expect to see those
explained and worked.

On Tue, Oct 17, 2023, 10:08 AM Clemens Backes  wrote:

> Contact emailscleme...@google.com
>
> ExplainerWe are ready for shipping the Multi-Memory proposal for
> WebAssembly, which recently moved to phase 4 according to the WebAssembly
> W3C process.
>
> Specification
> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>
> Design docs
> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>
> Summary
>
> Add support for more than one memory per WebAssembly module as specified
> in the WebAssembly Multi-Memory proposal:
> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>
> Blink componentBlink>JavaScript>WebAssembly
> 
>
> Search tagsWasm , WebAssembly
> , Multi-Memory
> 
>
> TAG reviewNot required as per: https://v8.dev/docs/feature-launch-process.
> TAG review statusNot applicable
>
> Risks
>
> Interoperability and Compatibility
>
> None
>
>
> *Gecko*: Positive
>
> *WebKit*: Positive
>
> *Web developers*: Strongly positive (
> https://github.com/WebAssembly/proposals)
>
> *Other signals*: This was voted to phase 4 (standardization) at the
> October 2023 WebAssembly Community Group meeting. 38 of 43 votes were
> "strongly for".
>
> 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?
>
> None
>
>
> Debuggability
>
> All memories are inspectable from DevTools, just like the first memory.
>
> 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
> 
> ?
>
> The WebAssembly proposal comes with all relevant tests; we pass them.
>
> Flag name on chrome://flagsenable-experimental-webassembly-features
>
> Finch feature nameNone
>
> Non-finch justificationNone
>
> Requires code in //chrome?False
>
> Tracking bughttps://crbug.com/v8/13918
>
> Estimated milestones
> Shipping on desktop 120
> DevTrial on desktop 117
> Shipping on Android 120
> DevTrial on Android 117
> Shipping on WebView 120
> Shipping on WebView 120
> DevTrial on iOS 117
>
> Anticipated spec changes
>
> None.
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5106389887746048
>
>
> 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/CAGO%3DqhA9xWgZXnGbC%2BYQ9XqJUmLwgxsyggKa9mGhsY%3DOXpzcsg%40mail.gmail.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+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAA44PQhQUuNSjxRR3cvOvYT%3D5Jhpy2bT__EVqKiCAPN7vXvFeQ%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: WebAssembly Multi-Memory

2023-10-17 Thread Clemens Backes 
On Tue, Oct 17, 2023 at 7:42 PM Alex Russell 
wrote:

> It's unclear why the TAG is not being informed or consulted. This has deep
> architectural implications for DOM integration and I'd expect to see those
> explained and worked.
>

As written in the ITS, a TAG review is not required as per
https://v8.dev/docs/feature-launch-process#tag. The changes to the
WebAssembly JS API are actually very minimal: Instead of one exported
memory, you can now have multiple.

I don't see any implication for anything DOM related (but I am also not
entirely sure what you mean by "DOM integration", there is nothing like
this planned in WebAssembly). Can you elaborate on that?


> On Tue, Oct 17, 2023, 10:08 AM Clemens Backes 
> wrote:
>
>> Contact emailscleme...@google.com
>>
>> ExplainerWe are ready for shipping the Multi-Memory proposal for
>> WebAssembly, which recently moved to phase 4 according to the WebAssembly
>> W3C process.
>>
>> Specification
>> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>>
>> Design docs
>> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>>
>> Summary
>>
>> Add support for more than one memory per WebAssembly module as specified
>> in the WebAssembly Multi-Memory proposal:
>> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>>
>> Blink componentBlink>JavaScript>WebAssembly
>> 
>>
>> Search tagsWasm ,
>> WebAssembly ,
>> Multi-Memory 
>>
>> TAG reviewNot required as per: https://v8.dev/docs/feature-launch-process
>> .
>> TAG review statusNot applicable
>>
>> Risks
>>
>> Interoperability and Compatibility
>>
>> None
>>
>>
>> *Gecko*: Positive
>>
>> *WebKit*: Positive
>>
>> *Web developers*: Strongly positive (
>> https://github.com/WebAssembly/proposals)
>>
>> *Other signals*: This was voted to phase 4 (standardization) at the
>> October 2023 WebAssembly Community Group meeting. 38 of 43 votes were
>> "strongly for".
>>
>> 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?
>>
>> None
>>
>>
>> Debuggability
>>
>> All memories are inspectable from DevTools, just like the first memory.
>>
>> 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
>> 
>> ?
>>
>> The WebAssembly proposal comes with all relevant tests; we pass them.
>>
>> Flag name on chrome://flagsenable-experimental-webassembly-features
>>
>> Finch feature nameNone
>>
>> Non-finch justificationNone
>>
>> Requires code in //chrome?False
>>
>> Tracking bughttps://crbug.com/v8/13918
>>
>> Estimated milestones
>> Shipping on desktop 120
>> DevTrial on desktop 117
>> Shipping on Android 120
>> DevTrial on Android 117
>> Shipping on WebView 120
>> Shipping on WebView 120
>> DevTrial on iOS 117
>>
>> Anticipated spec changes
>>
>> None.
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5106389887746048
>>
>>
>> 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/CAGO%3DqhA9xWgZXnGbC%2BYQ9XqJUmLwgxsyggKa9mGhsY%3DOXpzcsg%40mail.gmail.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+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGO%3DqhCQURi3QHH_NHKLHTz_-S5gZsuCLsKEYaL9uX3kupeseQ%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: WebAssembly Multi-Memory

2023-10-25 Thread Clemens Backes 
There has not been an update on this ITS in 8 days. What's the expected
timeline to get the LGTMs?

As the M120 branch cut is around the corner, I'll go ahead and prepare the
launch, given that this is a feature voted to phase 4 in the W3C
WebAssembly Community Group and all other approvals are there.

On Tue, Oct 17, 2023 at 8:09 PM Clemens Backes 
wrote:

> On Tue, Oct 17, 2023 at 7:42 PM Alex Russell 
> wrote:
>
>> It's unclear why the TAG is not being informed or consulted. This has
>> deep architectural implications for DOM integration and I'd expect to see
>> those explained and worked.
>>
>
> As written in the ITS, a TAG review is not required as per
> https://v8.dev/docs/feature-launch-process#tag. The changes to the
> WebAssembly JS API are actually very minimal: Instead of one exported
> memory, you can now have multiple.
>
> I don't see any implication for anything DOM related (but I am also not
> entirely sure what you mean by "DOM integration", there is nothing like
> this planned in WebAssembly). Can you elaborate on that?
>
>
>> On Tue, Oct 17, 2023, 10:08 AM Clemens Backes 
>> wrote:
>>
>>> Contact emailscleme...@google.com
>>>
>>> ExplainerWe are ready for shipping the Multi-Memory proposal for
>>> WebAssembly, which recently moved to phase 4 according to the WebAssembly
>>> W3C process.
>>>
>>> Specification
>>> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>>>
>>> Design docs
>>> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>>>
>>> Summary
>>>
>>> Add support for more than one memory per WebAssembly module as specified
>>> in the WebAssembly Multi-Memory proposal:
>>> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>>>
>>> Blink componentBlink>JavaScript>WebAssembly
>>> 
>>>
>>> Search tagsWasm ,
>>> WebAssembly ,
>>> Multi-Memory 
>>>
>>> TAG reviewNot required as per:
>>> https://v8.dev/docs/feature-launch-process.
>>> TAG review statusNot applicable
>>>
>>> Risks
>>>
>>> Interoperability and Compatibility
>>>
>>> None
>>>
>>>
>>> *Gecko*: Positive
>>>
>>> *WebKit*: Positive
>>>
>>> *Web developers*: Strongly positive (
>>> https://github.com/WebAssembly/proposals)
>>>
>>> *Other signals*: This was voted to phase 4 (standardization) at the
>>> October 2023 WebAssembly Community Group meeting. 38 of 43 votes were
>>> "strongly for".
>>>
>>> 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?
>>>
>>> None
>>>
>>>
>>> Debuggability
>>>
>>> All memories are inspectable from DevTools, just like the first memory.
>>>
>>> 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
>>> 
>>> ?
>>>
>>> The WebAssembly proposal comes with all relevant tests; we pass them.
>>>
>>> Flag name on chrome://flagsenable-experimental-webassembly-features
>>>
>>> Finch feature nameNone
>>>
>>> Non-finch justificationNone
>>>
>>> Requires code in //chrome?False
>>>
>>> Tracking bughttps://crbug.com/v8/13918
>>>
>>> Estimated milestones
>>> Shipping on desktop 120
>>> DevTrial on desktop 117
>>> Shipping on Android 120
>>> DevTrial on Android 117
>>> Shipping on WebView 120
>>> Shipping on WebView 120
>>> DevTrial on iOS 117
>>>
>>> Anticipated spec changes
>>>
>>> None.
>>>
>>> Link to entry on the Chrome Platform Status
>>> https://chromestatus.com/feature/5106389887746048
>>>
>>>
>>> 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/CAGO%3DqhA9xWgZXnGbC%2BYQ9XqJUmLwgxsyggKa9mGhsY%3DOXpzcsg%40mail.gmail.com
>>> 
>>> .
>>>
>>
>
>

-- 

Clemens Backes

Software Engineer

cleme...@google.com

Google Germany GmbH

Erika-Mann-Straße 33

80636 München

Geschäftsführer: Paul Manicle, Liana Sebastian

Registergericht und -nummer: Hamburg, HRB 86891

Sitz der Gesellschaft: Hamburg

Diese E-Mail ist vertraulich. Falls sie diese fälschlicherweise erhalten
haben

Re: [blink-dev] Intent to Ship: WebAssembly Multi-Memory

2023-10-25 Thread Yoav Weiss 
LGTM1

On Wednesday, October 25, 2023 at 4:24:04 PM UTC+2 Clemens Backes wrote:

> There has not been an update on this ITS in 8 days. What's the expected 
> timeline to get the LGTMs?
>
> As the M120 branch cut is around the corner, I'll go ahead and prepare the 
> launch, given that this is a feature voted to phase 4 in the W3C 
> WebAssembly Community Group and all other approvals are there.
>
> On Tue, Oct 17, 2023 at 8:09 PM Clemens Backes  
> wrote:
>
>> On Tue, Oct 17, 2023 at 7:42 PM Alex Russell  
>> wrote:
>>
>>> It's unclear why the TAG is not being informed or consulted. This has 
>>> deep architectural implications for DOM integration and I'd expect to see 
>>> those explained and worked.
>>>
>>
>> As written in the ITS, a TAG review is not required as per 
>> https://v8.dev/docs/feature-launch-process#tag. The changes to the 
>> WebAssembly JS API are actually very minimal: Instead of one exported 
>> memory, you can now have multiple.
>>
>> I don't see any implication for anything DOM related (but I am also not 
>> entirely sure what you mean by "DOM integration", there is nothing like 
>> this planned in WebAssembly). Can you elaborate on that?
>>
>>
>>> On Tue, Oct 17, 2023, 10:08 AM Clemens Backes  
>>> wrote:
>>>
 Contact emailscleme...@google.com

 ExplainerWe are ready for shipping the Multi-Memory proposal for 
 WebAssembly, which recently moved to phase 4 according to the WebAssembly 
 W3C process.

 Specification
 https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md

 Design docs
 https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md

 Summary

 Add support for more than one memory per WebAssembly module as 
 specified in the WebAssembly Multi-Memory proposal: 
 https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md

 Blink componentBlink>JavaScript>WebAssembly 
 

 Search tagsWasm , 
 WebAssembly , 
 Multi-Memory 

 TAG reviewNot required as per: 
 https://v8.dev/docs/feature-launch-process.
 TAG review statusNot applicable

 Risks

 Interoperability and Compatibility

 None


 *Gecko*: Positive

 *WebKit*: Positive

 *Web developers*: Strongly positive (
 https://github.com/WebAssembly/proposals)

 *Other signals*: This was voted to phase 4 (standardization) at the 
 October 2023 WebAssembly Community Group meeting. 38 of 43 votes were 
 "strongly for".

 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?

 None


 Debuggability

 All memories are inspectable from DevTools, just like the first memory.

 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 
 
 ?

 The WebAssembly proposal comes with all relevant tests; we pass them.

 Flag name on chrome://flagsenable-experimental-webassembly-features

 Finch feature nameNone

 Non-finch justificationNone

 Requires code in //chrome?False

 Tracking bughttps://crbug.com/v8/13918

 Estimated milestones
 Shipping on desktop 120
 DevTrial on desktop 117
 Shipping on Android 120
 DevTrial on Android 117
 Shipping on WebView 120
 Shipping on WebView 120
 DevTrial on iOS 117

 Anticipated spec changes

 None.

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


 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/CAGO%3DqhA9xWgZXnGbC%2BYQ9XqJUmLwgxsyggKa9mGhsY%3DOXpzcsg%40mail.gmail.com
  
 
 .

>>>
>>
>>
>
> -- 
>
> Clemens Backes
>
> Software Engineer
>
> cleme.

Re: [blink-dev] Intent to Ship: WebAssembly Multi-Memory

2023-10-25 Thread Chris Harrelson 
LGTM2

On Wed, Oct 25, 2023 at 8:23 AM Yoav Weiss  wrote:

> LGTM1
>
> On Wednesday, October 25, 2023 at 4:24:04 PM UTC+2 Clemens Backes wrote:
>
>> There has not been an update on this ITS in 8 days. What's the expected
>> timeline to get the LGTMs?
>>
>
Last week was BlinkOn and we do most reviews in our weekly meeting on
Wednesdays.


>
>> As the M120 branch cut is around the corner, I'll go ahead and prepare
>> the launch, given that this is a feature voted to phase 4 in the W3C
>> WebAssembly Community Group and all other approvals are there.
>>
>> On Tue, Oct 17, 2023 at 8:09 PM Clemens Backes 
>> wrote:
>>
>>> On Tue, Oct 17, 2023 at 7:42 PM Alex Russell 
>>> wrote:
>>>
 It's unclear why the TAG is not being informed or consulted. This has
 deep architectural implications for DOM integration and I'd expect to see
 those explained and worked.

>>>
>>> As written in the ITS, a TAG review is not required as per
>>> https://v8.dev/docs/feature-launch-process#tag. The changes to the
>>> WebAssembly JS API are actually very minimal: Instead of one exported
>>> memory, you can now have multiple.
>>>
>>> I don't see any implication for anything DOM related (but I am also not
>>> entirely sure what you mean by "DOM integration", there is nothing like
>>> this planned in WebAssembly). Can you elaborate on that?
>>>
>>>
 On Tue, Oct 17, 2023, 10:08 AM Clemens Backes 
 wrote:

> Contact emailscleme...@google.com
>
> ExplainerWe are ready for shipping the Multi-Memory proposal for
> WebAssembly, which recently moved to phase 4 according to the WebAssembly
> W3C process.
>
> Specification
> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>
> Design docs
> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>
> Summary
>
> Add support for more than one memory per WebAssembly module as
> specified in the WebAssembly Multi-Memory proposal:
> https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md
>
> Blink componentBlink>JavaScript>WebAssembly
> 
>
> Search tagsWasm ,
> WebAssembly ,
> Multi-Memory 
>
> TAG reviewNot required as per:
> https://v8.dev/docs/feature-launch-process.
> TAG review statusNot applicable
>
> Risks
>
> Interoperability and Compatibility
>
> None
>
>
> *Gecko*: Positive
>
> *WebKit*: Positive
>
> *Web developers*: Strongly positive (
> https://github.com/WebAssembly/proposals)
>
> *Other signals*: This was voted to phase 4 (standardization) at the
> October 2023 WebAssembly Community Group meeting. 38 of 43 votes were
> "strongly for".
>
> 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?
>
> None
>
>
> Debuggability
>
> All memories are inspectable from DevTools, just like the first memory.
>
> 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
> 
> ?
>
> The WebAssembly proposal comes with all relevant tests; we pass them.
>
> Flag name on chrome://flagsenable-experimental-webassembly-features
>
> Finch feature nameNone
>
> Non-finch justificationNone
>
> Requires code in //chrome?False
>
> Tracking bughttps://crbug.com/v8/13918
>
> Estimated milestones
> Shipping on desktop 120
> DevTrial on desktop 117
> Shipping on Android 120
> DevTrial on Android 117
> Shipping on WebView 120
> Shipping on WebView 120
> DevTrial on iOS 117
>
> Anticipated spec changes
>
> None.
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5106389887746048
>
>
> 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/CAGO%3DqhA9xWgZXnGbC%2BYQ9XqJUmLwgxsyggKa9mGhsY%3DOXpzcsg%40mail.gmail.com
>

Re: [blink-dev] Intent to Ship: WebAssembly Multi-Memory

2023-10-25 Thread Mike Taylor 

LGTM3

On 10/25/23 11:25 AM, Chris Harrelson wrote:

LGTM2

On Wed, Oct 25, 2023 at 8:23 AM Yoav Weiss  wrote:

LGTM1

On Wednesday, October 25, 2023 at 4:24:04 PM UTC+2 Clemens Backes
wrote:

There has not been an update on this ITS in 8 days. What's the
expected timeline to get the LGTMs?


Last week was BlinkOn and we do most reviews in our weekly meeting on 
Wednesdays.



As the M120 branch cut is around the corner, I'll go ahead and
prepare the launch, given that this is a feature voted to
phase 4 in the W3C WebAssembly Community Group and all other
approvals are there.

On Tue, Oct 17, 2023 at 8:09 PM Clemens Backes
 wrote:

On Tue, Oct 17, 2023 at 7:42 PM Alex Russell
 wrote:

It's unclear why the TAG is not being informed or
consulted. This has deep architectural implications
for DOM integration and I'd expect to see those
explained and worked.


As written in the ITS, a TAG review is not required as per
https://v8.dev/docs/feature-launch-process#tag. The
changes to the WebAssembly JS API are actually very
minimal: Instead of one exported memory, you can now have
multiple.

I don't see any implication for anything DOM related (but
I am also not entirely sure what you mean by "DOM
integration", there is nothing like this planned in
WebAssembly). Can you elaborate on that?


On Tue, Oct 17, 2023, 10:08 AM Clemens Backes
 wrote:


Contact emails

cleme...@google.com


Explainer

We are ready for shipping the Multi-Memory
proposal for WebAssembly, which recently moved to
phase 4 according to the WebAssembly W3C process.


Specification


https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md


Design docs


https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md


Summary

Add support for more than one memory per
WebAssembly module as specified in the WebAssembly
Multi-Memory proposal:

https://github.com/WebAssembly/multi-memory/blob/main/proposals/multi-memory/Overview.md


Blink component

Blink>JavaScript>WebAssembly




Search tags

Wasm
,
WebAssembly
,
Multi-Memory



TAG review


Not required as per:
https://v8.dev/docs/feature-launch-process.


TAG review status

Not applicable


Risks


Interoperability and Compatibility

None



/Gecko/: Positive

/WebKit/: Positive

/Web developers/: Strongly positive
(https://github.com/WebAssembly/proposals)

/Other signals/: This was voted to phase 4
(standardization) at the October 2023 WebAssembly
Community Group meeting. 38 of 43 votes were
"strongly for".


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?

None



Debuggability

All memories are inspectable from DevTools, just
like the first memory.


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

?

The WebAssembly proposal comes with all relevant
tests;