Re: [blink-dev] Intent to Ship: Promise.try

2024-07-03 Thread Shu-yu Guo 
On Tue, Jul 2, 2024 at 9:23 PM Domenic Denicola 
wrote:

> On Wed, Jul 3, 2024 at 7:25 AM Shu-yu Guo  wrote:
>
>> Contact emails...@chromium.org
>>
>> ExplainerNone
>>
>
> I think https://github.com/tc39/proposal-promise-try/blob/main/README.md
> probably qualifies here.
>
>
>>
>> Specificationhttps://tc39.es/proposal-promise-try
>>
>> Summary
>>
>> Promise.try is a new static method. `Promise.try(f)` is shorthand for
>> `new Promise(resolve => resolve(f()))`.
>>
>>
>> Blink componentBlink>JavaScript>Language
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EJavaScript%3ELanguage>
>>
>> TAG reviewNone
>>
>> TAG review statusNot applicable
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>> None. This is a new static method on the Promise constructor.
>>
>>
>> *Gecko*: Positive This is a Stage 3 TC39 proposal.
>>
>> *WebKit*: Positive (https://bugs.webkit.org/show_bug.cgi?id=275359) This
>> is a Stage 3 TC39 proposal.
>>
>
> The repository currently says "stage 2.7", whereas our exceptions for TAG
> review and a lot of the usual Blink process relies on the proposal being in
> stage 3.
>
> From what I can tell of https://tc39.es/process-document/ the difference
> is that stage 3 has sufficient test262 tests? But below you say that the
> feature is fully tested by test262 tests, so I'm unsure what's holding this
> back from stage 3.
>
> In practice I suspect this isn't a real problem, but I don't want to LGTM
> right away until we get a bit more clarity here, and possibly update the
> relevant Blink process bits.
>

I think the repo is not updated. This received Stage 3 at the June 2024
meeting, but the notes are not yet public.


>
>
>
>>
>> *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?
>>
>> None
>>
>>
>> Debuggability
>>
>> None
>>
>>
>> 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
>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>> ?Yes
>>
>> Test262:
>> https://github.com/tc39/test262/tree/main/test/built-ins/Promise/try
>>
>>
>> Flag name on chrome://flags--js-promise-try
>>
>> Finch feature namekJavaScriptPromiseTry
>>
>> Requires code in //chrome?False
>>
>> Estimated milestones
>> DevTrial on desktop 128
>> DevTrial on Android 128
>>
>> 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).
>> None
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/6315704705089536?gate=5106880681869312
>>
>> 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+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e-DDG5a-Q1d0955b15kS-hSPx91vpHqrdv61yUAiCyarg%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e-DDG5a-Q1d0955b15kS-hSPx91vpHqrdv61yUAiCyarg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e-r2ioCiTrxf-7gjND69%2BE2XhQGye_%2BdL0Kvy5_7SnkYQ%40mail.gmail.com.

[blink-dev] Intent to Ship: Promise.try

2024-07-02 Thread Shu-yu Guo 
Contact emails...@chromium.org

ExplainerNone

Specificationhttps://tc39.es/proposal-promise-try

Summary

Promise.try is a new static method. `Promise.try(f)` is shorthand for `new
Promise(resolve => resolve(f()))`.


Blink componentBlink>JavaScript>Language


TAG reviewNone

TAG review statusNot applicable

Risks


Interoperability and Compatibility

None. This is a new static method on the Promise constructor.


*Gecko*: Positive This is a Stage 3 TC39 proposal.

*WebKit*: Positive (https://bugs.webkit.org/show_bug.cgi?id=275359) This is
a Stage 3 TC39 proposal.

*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?

None


Debuggability

None


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

?Yes

Test262:
https://github.com/tc39/test262/tree/main/test/built-ins/Promise/try


Flag name on chrome://flags--js-promise-try

Finch feature namekJavaScriptPromiseTry

Requires code in //chrome?False

Estimated milestones
DevTrial on desktop 128
DevTrial on Android 128

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).
None

Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/6315704705089536?gate=5106880681869312

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/CAN-e9e-DDG5a-Q1d0955b15kS-hSPx91vpHqrdv61yUAiCyarg%40mail.gmail.com.

[blink-dev] Intent to Ship: RegExp modifiers

2024-03-27 Thread &#x27;Shu-yu Guo' via blink-dev 
Contact emails...@chromium.org, pth...@chromium.org

ExplainerNone

Specificationhttps://tc39.es/proposal-regexp-modifiers

Summary

RegExp modifiers adds the ability to locally modify the 'i', 'm', and 's'
flags inside a pattern. To enable a flag for a subexpression, use
`(?X:subexpr)` where X is one of 'i', 'm', or 's'. To disable a flag for a
subexpression, use `(-X:subexpr)`. For example, for the case-insensitivity
'i' flag: ``` const re1 = /^[a-z](?-i:[a-z])$/i; re1.test("ab"); // true
re1.test("Ab"); // true re1.test("aB"); // false const re2 =
/^(?i:[a-z])[a-z]$/; re2.test("ab"); // true re2.test("Ab"); // true
re2.test("aB"); // false ```


Blink componentBlink>JavaScript>Regexp


TAG reviewNone

TAG review statusNot applicable

Risks


Interoperability and Compatibility

No interoperability risk. This is a Stage 3 TC39 proposal.


*Gecko*: Positive TC39 Stage 3

*WebKit*: Positive TC39 Stage 3

*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?

None


Debuggability

No special needs. JS RegExps already debuggable.


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

?Yes

In test262: https://github.com/tc39/test262/pull/3960


Flag name on chrome://flags--js-regexp-modifiers

Finch feature nameJavaScriptRegExpModifiers

Requires code in //chrome?False

Estimated milestones
DevTrial on desktop 122
DevTrial on Android 122

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).
None

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

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/CAN-e9e948%3DQSg6zskRN25JGkvxXVP67RDkXHvijzBRueP1DnzA%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: RegExp duplicate named capture groups

2024-03-11 Thread Shu-yu Guo 
On Mon, Mar 11, 2024 at 8:26 AM Mike Taylor  wrote:

> On 3/11/24 6:49 AM, Yoav Weiss (@Shopify) wrote:
>
>
>
> On Fri, Mar 8, 2024 at 4:26 PM Mike Taylor  wrote:
>
>> LGTM1
>> On 3/7/24 6:22 PM, Shu-yu Guo wrote:
>>
>> Contact emails pth...@chromium.org, s...@chromium.org
>>
>> Explainer None
>>
>> Specification https://github.com/tc39/ecma262/pull/2721
>>
>>
> What are the implications of this on regexes that already have duplicate
> named capture groups? Would their behavior change?
>
> Shu can confirm, but my understanding is any regexes in the wild that have
> duplicate named capture groups today are just busted (they should throw a
> SyntaxError - and those are pretty hard to miss). If they do exist in the
> wild, they should start working, which in theory would match author intent.
> The risk seems very low IMHO, if it exists at all.
>

Exactly right. This is a case of going from a SyntaxError to working, so
there should be no back compat issues.

The concrete example from the explainer currently throws a SyntaxError:

```
/(?[0-9]{4})-[0-9]{2}|[0-9]{2}-(?[0-9]{4})/
^^^
SyntaxError: Invalid regular expression:
/(?[0-9]{4})-[0-9]{2}|[0-9]{2}-(?[0-9]{4})/: Duplicate capture
group name
```


>>
>> Summary
>>
>> https://github.com/tc39/proposal-duplicate-named-capturing-groups
>>
>>
>> Blink component Blink>JavaScript>Regexp
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EJavaScript%3ERegexp>
>>
>> TAG review None
>>
>> TAG review status Not applicable
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>> This is a Stage 3 TC39 proposal. No known interop risk. No known web
>> incompatibility risk.
>>
>>
>> *Gecko*: Positive Firefox uses V8's regexp engine, so it is not actually
>> an independent implementation here.
>>
>> *WebKit*: Shipped/Shipping (
>> https://bugs.webkit.org/show_bug.cgi?id=252553) Stage 3 TC39 proposal.
>>
>> *Web developers*: No signals
>>
>> *Other signals*:
>>
>> Ergonomics
>>
>> No known ergonomics risks.
>>
>>
>> Activation
>>
>> This is unlikely to be polyfillable since it's adding a new kind of
>> RegExp syntax.
>>
>>
>> Security
>>
>> No known security risks.
>>
>>
>> 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
>>
>> Debuggable like any other JS RegExp.
>>
>>
>> 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
>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>> ? Yes
>>
>> Tested in test262. https://github.com/tc39/test262/pull/3625
>> https://github.com/tc39/test262/pull/3706
>> https://github.com/tc39/test262/pull/3709
>>
>>
>> Flag name on chrome://flags --js-regexp-duplicate-named-groups
>>
>> Finch feature name None
>>
>> Non-finch justification None
>>
>> Requires code in //chrome? False
>>
>> Estimated milestones
>> DevTrial on desktop 123
>> DevTrial on Android 123
>>
>> 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).
>> None
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5149208388829184
>>
>> 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+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e_1DaU400sEcpB6RGv3pZg_382WduoF9MPZvK8QTPfdSQ%40mail.gmail.com
>> <https://groups.go

[blink-dev] Intent to Ship: RegExp duplicate named capture groups

2024-03-07 Thread Shu-yu Guo 
Contact emailspth...@chromium.org, s...@chromium.org

ExplainerNone

Specificationhttps://github.com/tc39/ecma262/pull/2721

Summary

https://github.com/tc39/proposal-duplicate-named-capturing-groups


Blink componentBlink>JavaScript>Regexp


TAG reviewNone

TAG review statusNot applicable

Risks


Interoperability and Compatibility

This is a Stage 3 TC39 proposal. No known interop risk. No known web
incompatibility risk.


*Gecko*: Positive Firefox uses V8's regexp engine, so it is not actually an
independent implementation here.

*WebKit*: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=252553)
Stage 3 TC39 proposal.

*Web developers*: No signals

*Other signals*:

Ergonomics

No known ergonomics risks.


Activation

This is unlikely to be polyfillable since it's adding a new kind of RegExp
syntax.


Security

No known security risks.


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

Debuggable like any other JS RegExp.


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

?Yes

Tested in test262. https://github.com/tc39/test262/pull/3625
https://github.com/tc39/test262/pull/3706
https://github.com/tc39/test262/pull/3709


Flag name on chrome://flags--js-regexp-duplicate-named-groups

Finch feature nameNone

Non-finch justificationNone

Requires code in //chrome?False

Estimated milestones
DevTrial on desktop 123
DevTrial on Android 123

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).
None

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

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/CAN-e9e_1DaU400sEcpB6RGv3pZg_382WduoF9MPZvK8QTPfdSQ%40mail.gmail.com.

[blink-dev] Request for API OWNERs' feedback for microwaiting in JS

2024-01-05 Thread Shu-yu Guo 
Hello blink API OWNERs,

I'm requesting early feedback on
https://github.com/syg/proposal-atomics-microwait. Specifically, the
clampTimeoutIfCannotBlock option
,
as it proposes relaxing the "main thread cannot block" restriction.

NB This is not yet (but will be) presented at TC39 in February.

Thanks,
shu

-- 
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/CAN-e9e-%3DqgbB96AOx48%2BC7Ni4he%3DEJaNi4fyDQRkCktPb%2B3bdg%40mail.gmail.com.

[blink-dev] Intent to Prototype: Deprecate and remove import assertion 'assert' syntax

2023-11-15 Thread Shu-yu Guo 
Contact emails...@chromium.org, nriba...@igalia.com

ExplainerNone

Specificationhttps://tc39.es/proposal-import-attributes

Summary

TC39 has consensus for trying to deprecate and remove the `assert` keyword
in favor of the new `with` keyword in import attribute syntax. That is,
`import m from 'foo' assert { type: 'json' }` will now throw a SyntaxError,
and developers must change to `import m from 'foo' with { type: 'json' }`.
https://github.com/tc39/proposal-import-attributes/issues/135


Blink componentBlink>JavaScript>Language


Motivation

The import assertions proposal (now called "import attributes") [1] in TC39
shipped in M91 with the `import mod from 'foo' assert { type: 'json' }`
syntax. The original semantics was that additional information following
the `assert` keyword cannot cause the module to be reinterpreted or change
the semantics of the module in any way, i.e., a pure assertion. Following
an HTML integration issue with CSP [2] that required changing Accept
headers depending on the requested module type, TC39 reached consensus that
the "pure assertion" semantics are to be relaxed to allow reinterpretation,
and that the `assert` keyword be changed to `with` to reflect the new
semantics. [1] https://github.com/tc39/proposal-import-attributes/ [2]
https://github.com/whatwg/html/issues/7233


Initial public proposalNone

TAG reviewNone

TAG review statusNot applicable

Risks


Interoperability and Compatibility

There is no interoperability risk because Safari and Firefox never shipped
the `assert` syntax. There is compatibility risk within Chrome as we
shipped in M91.


*Gecko*: N/A

*WebKit*: N/A

*Web developers*: No signals

*Other signals*:

Ergonomics

None.


Activation

None.


Security

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?

None


Debuggability

None.


Is this feature fully tested by web-platform-tests

?In test262

Flag name on chrome://flags--harmony-import-assertions

Finch feature nameNone

Non-finch justification

Use counter metric shows current usage at 0.0002%
https://chromestatus.com/metrics/feature/timeline/popularity/4528
Additionally, analysis shows that sites that do use it have fallbacks:
https://github.com/tc39/proposal-import-attributes/issues/135#issuecomment-1625217926
This data suggests that a finch trial is not needed, and a clean removal is
possible.


Requires code in //chrome?False

Estimated milestones

No milestones specified


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

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/CAN-e9e_cMbiPO2AhV%3D%3DP_r%3Dov%2BKvxyXqkyosej9a%3DuJO7zt5_Q%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: Array.fromAsync

2023-10-25 Thread Shu-yu Guo 
Those gates are not applicable for most TC39 stage 3 features, including
this one. Are you asking them to be marked as such or that we requested
reviews for it?

On Wed, Oct 25, 2023 at 4:00 PM Mike Taylor  wrote:

> Oops... sent too early. Can you also please request reviews for the rest
> of the review gates
> 
> in the chromestatus entry?
> On 10/25/23 6:57 PM, Mike Taylor wrote:
>
> LGTM1. It's encouraging that Firefox Nightly shipped this a few months
> back  with no
> reported regressions thus far.
> On 10/25/23 6:39 PM, Rezvan Mahdavi Hezaveh wrote:
>
> Contact emails s...@chromium.org, rez...@chromium.org
>
> Explainer https://github.com/tc39/proposal-array-from-async
>
> Specification https://tc39.es/proposal-array-from-async
>
> Summary
>
> Array.fromAsync is the async version of Array.from. It takes async
> iterables, iterates them, and collects the results into an array.
>
>
> Blink component Blink>JavaScript>Language
> 
>
> TAG review None
>
> TAG review status Not applicable
>
> Risks
>
>
> Interoperability and Compatibility
>
> No known interop or web compat risk.
>
>
> *Gecko*: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1746209)
> This is a TC39 Stage 3 proposal.
>
> *WebKit*: Positive This is a TC39 Stage 3 proposal.
>
> *Web developers*: Positive (
> https://twitter.com/erickwendel_/status/1555206623836127232) Seems
> positive, lots of likes on Twitter.
>
> *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?
>
> None
>
>
> Debuggability
>
> It is debugged as any other static method in JavaScript.
>
>
> 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
>
> https://github.com/tc39/test262/issues/3725
>
>
> Flag name on chrome://flags --harmony_array_from_async
>
> Finch feature name None
>
> Non-finch justification None
>
> Requires code in //chrome? False
>
> Tracking bug https://bugs.chromium.org/p/v8/issues/detail?id=13321
>
> Estimated milestones
> DevTrial on desktop 120
> DevTrial on Android 120
>
> 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).
> None
>
> Link to entry on the Chrome Platform Status
> https://chromestatus.com/feature/5069575759069184
>
> 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/CACJ3t%2Bg4MwKGhiGJg%2B0WdgJXTD0rGJ22ZFGAF8bnOtGoLhszzA%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/591771b3-56e8-4f56-aba2-f66241221d29%40chromium.org
> 
> .
>

-- 
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/CAN-e9e_2hjvbBo5Bhpy7PfzxvEMH90ZnK%2B5_i8YQ2PoKFaS_bw%40mail.gmail.com.

[blink-dev] Intent to Ship: Promise.withResolvers

2023-09-14 Thread &#x27;Shu-yu Guo' via blink-dev 
Contact emails...@chromium.org

ExplainerNone

Specificationhttps://tc39.es/proposal-promise-with-resolvers

Summary

Promise.withResolvers is a static methods that returns a new Promise along
with its resolver functions, i.e. `const { promise, resolve, reject } =
Promise.withResolvers()`. This is a standard version of a common helper
function found in many JS libraries. Historically, some may know it as
`defer` or `deferred`.


Blink componentBlink>JavaScript>Language


TAG reviewNone

TAG review statusNot applicable

Risks


Interoperability and Compatibility

Very little risk. This is a new static method on the Promise constructor.


*Gecko*: Positive This is a Stage 3 TC39 proposal.

*WebKit*: Positive (https://bugs.webkit.org/show_bug.cgi?id=259153) This is
a Stage 3 TC39 proposal.

*Web developers*: Positive

*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?

None


Debuggability



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

?In test262

.

Flag name on chrome://flags--js-promise-withresolvers

Finch feature nameJavaScriptPromiseWithResolvers

Requires code in //chrome?False

Estimated milestones
Shipping on desktop 119
DevTrial on desktop 117
Shipping on Android 119
DevTrial on Android 117

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).
None

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

Links to previous Intent discussions

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/CAN-e9e-C0T4tV-8kOVfYZVG1nL9wXqK-twi-Tj3fFp3K8V398Q%40mail.gmail.com.

[blink-dev] Intent to Ship: Array grouping

2023-07-11 Thread Shu-yu Guo 
Contact emails
s...@chromium.org

Explainerhttps://github.com/tc39/proposal-array-grouping/blob/main/README.md

Specificationhttps://tc39.es/proposal-array-grouping/

Summary

Adds news Object.groupBy(iterable, groupCallback) and Map.groupBy(iterable,
groupCallback) to perform a grouping or bucketing operation. The Object
method returns a plain object, where the groups are property keys. The Map
method returns a Map, where the keys can be arbitrary values.


Blink componentBlink>JavaScript>Language


TAG review

TAG review statusNot applicable

Risks


Interoperability and Compatibility

Minimal. These are static methods on Object and Map, which are very
unlikely to cause incompat. The previous Array.prototype version caused
significant compat issues and the proposal was redesigned.


*Gecko*: Shipped/Shipping (
https://bugzilla.mozilla.org/show_bug.cgi?id=1739648)

*WebKit*: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=234327)

*Web developers*: Strongly positive (
https://twitter.com/rauschma/status/1470854996459769867?s=20&t=DDr_7gzapEKcfF2MbEVzHA
)

*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?



Debuggability

This feature adds two new built-in Array.prototype methods, which are
debuggable like all other built-in methods.


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

?In test262:
https://github.com/tc39/test262/tree/main/test/built-ins/Object/prototype/groupBy
https://github.com/tc39/test262/tree/main/test/built-ins/Map/prototype/groupBy

Flag name on chrome://flags--harmony-array-grouping

Finch feature name

Non-finch justificationNone

Requires code in //chrome?False

Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=12499

Estimated milestones
DevTrial on desktop 100
DevTrial on Android 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/5714791975878656

Links to previous Intent discussionsNote that this is a new version of the
proposal, redesigned after web incompatibility prevented shipping in the
previous version and was unshipped by all the browsers. The previous I2S is
here

.

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/CAN-e9e94MKs3PgCqPG6E-7x_%2BfH8Z4AFLMC0Bva-dZrVBogKtA%40mail.gmail.com.

[blink-dev] Intent to Ship: ArrayBuffer.prototype.transfer

2023-03-29 Thread Shu-yu Guo 
Contact emails...@chromium.org

Explainerhttps://github.com/tc39/proposal-arraybuffer-transfer

Specificationhttps://tc39.es/proposal-arraybuffer-transfer

Design docs
N/A

Summary

Adds the ArrayBuffer.prototype.transfer method, which copies the receiver
buffer, detaches the receiver, then returns the copy. This adds a JS API
for what is possible via structured cloning. Also adds
ArrayBuffer.prototype.transferToFixedLength and the
ArrayBuffer.prototype.detached getter. This is a TC39 proposal.


Blink componentBlink>JavaScript>Language


TAG review

TAG review statusNot applicable

Risks


Interoperability and Compatibility

Very low. This is a new method on ArrayBuffer.prototype, which historically
has not had collision issues (unlike Array.prototype).


*Gecko*: Positive This is a Stage 3 TC39 proposal.

*WebKit*: Positive This is a Stage 3 TC39 proposal.

*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?

None.


Debuggability



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

?In test262, see tests/built-ins/ArrayBuffer/prototype/

{transfer,transferToFixedLength,detached}

Flag name--harmony-rab-gsab-transfer

Requires code in //chrome?False

Estimated milestones
Shipping on desktop 114
Shipping on Android 114

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).
None.

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

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/CAN-e9e-3%2BZpiD0ANVJFE7nKNO66Hr-aP6LgtwrjHEpcWrzmL2Q%40mail.gmail.com.

[blink-dev] Intent to Ship: JSON.parse source text access

2023-03-27 Thread Shu-yu Guo 
Contact emails...@chromium.org

Explainer
https://github.com/tc39/proposal-json-parse-with-source/blob/master/README.md

Specificationhttps://tc39.es/proposal-json-parse-with-source

Summary

This proposal adds an object with a "source" property that is passed as the
3rd argument to the reviver function in JSON.parse. This property contains
the raw source text for the value being parsed. It is designed to address
the issue that JSON parsing is lossy, e.g. around BigInt values. For
example, `JSON.parse(" ", (key, val, {source}) =>
BigInt(source))`.


Blink componentBlink>JavaScript>Language


TAG review

TAG review statusNot applicable

Risks


Interoperability and Compatibility



*Gecko*: Positive This is a Stage 3 TC39 proposal.

*WebKit*: Positive This is a Stage 3 TC39 proposal.

*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?



Debuggability

The 3rd argument being added will be debugged as any JavaScript function
argument.


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

?In test262: https://github.com/tc39/test262/pull/3806

Flag name--harmony-json-parse-with-source

Requires code in //chrome?False

Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=12955

Estimated milestones
Shipping on desktop 114
DevTrial on desktop 108
DevTrial on Android 108

Anticipated spec changes

None


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

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/CAN-e9e_i9snn_eZQ_eZgL-_%3DzTvBQZ1E4h_kxhVfKVSL892gCQ%40mail.gmail.com.

[blink-dev] Intent to Ship: String.prototype.isWellFormed and toWellFormed

2023-01-11 Thread &#x27;Shu-yu Guo' via blink-dev 
Contact emails...@chromium.org

Explainerhttps://github.com/tc39/proposal-is-usv-string/blob/main/README.md

Specificationhttps://tc39.es/proposal-is-usv-string

Summary

Add two String.prototype methods for working with well-formed UTF-16
strings. A JavaScript string value is well-formed UTF-16 if it has no
unpaired surrogate code points. By default, JavaScript strings may be
ill-formed. - String.prototype.isWellFormed returns whether the receiver
string is well-formed UTF-16. - String.prototype.toWellFormed returns a
string that is identical to the receiver string, except all unpaired
surrogate code points are replaced with U+FFFD (REPLACEMENT CHARACTER).


Blink componentBlink>JavaScript>Language


TAG review

TAG review statusNot applicable

Risks


Interoperability and Compatibility

No known compatibility risk. Though all additions to built-in prototypes
such as String.prototype carry non-zero risk in light of polyfill
libraries. No interoperability risk. This is a Stage 3 TC39 proposal.


*Gecko*: In development (
https://bugzilla.mozilla.org/show_bug.cgi?id=1803523)

*WebKit*: In development (https://bugs.webkit.org/show_bug.cgi?id=248588)

*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?



Debuggability

Debuggable like other built-in String methods.

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

?In test262 

Flag name--harmony-string-is-well-formed

Requires code in //chrome?False

Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=13557

Estimated milestones
DevTrial on desktop 111
DevTrial on Android 111

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/5200195346759680

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/CAN-e9e_CJVsBrz%2Bc-Ujb-XEEi4GOjayd1cR77v9EMs5RoCNW_g%40mail.gmail.com.

Re: [blink-dev] Re: List decorators on Chrome Status

2023-01-11 Thread Shu-yu Guo 
We'll be adding the decorators proposal soon. TC39 proposals are generally
added as work on them starts.

On Wed, Jan 11, 2023 at 12:03 PM Adam Klein  wrote:

> +Shu-yu Guo 
>
> On Wed, Jan 11, 2023 at 8:03 AM K. Moon  wrote:
>
>> My best guess would be https://github.com/tc39/proposal-decorators, but
>> that'd be a V8 question, not a Blink question.
>>
>> On Wed, Jan 11, 2023 at 7:43 AM 'Jason Robbins' via blink-dev <
>> blink-dev@chromium.org> wrote:
>>
>>> What do you mean by "decorators"?
>>>
>>> On Tuesday, January 10, 2023 at 5:54:04 PM UTC-8 tru...@gmail.com wrote:
>>>
>>>> I don't see "decorators" at https://chromestatus.com/newfeatures. Can
>>>> we add it? - Joe
>>>
>>> --
>>> 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/a6c78d37-9b9c-4e01-b4dd-0c5704ce920cn%40chromium.org
>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/a6c78d37-9b9c-4e01-b4dd-0c5704ce920cn%40chromium.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "blink-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to blink-dev+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACwGi-5raD%2Bf1q0mQsTvbg2iTR0RuQD4jcS3ogFh0RcbKj0DMg%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACwGi-5raD%2Bf1q0mQsTvbg2iTR0RuQD4jcS3ogFh0RcbKj0DMg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e9dcekF9KM-u1pkD8ceqhenmf%2B2%3DOmJNPRAfOoaLMm-Rg%40mail.gmail.com.

[blink-dev] Intent to Ship: Methods that change Array and TypedArray by copy

2022-11-08 Thread Shu-yu Guo 
Contact emails...@chromium.org

Explainerhttps://github.com/tc39/proposal-change-array-by-copy

Specificationhttps://tc39.es/proposal-change-array-by-copy

Summary

Provides additional methods on Array.prototype and TypedArray.prototype to
enable changes on the array by returning a new copy of it with the change.


Blink componentBlink>JavaScript>Language


TAG reviewTC39 proposal that only touches Array.prototype, without other
interactions with web APIs.

TAG review statusNot applicable

Risks


Interoperability and Compatibility

No interoperability risk as this is a TC39 proposal implemented in tandem
by browser engines. Minimal but non-zero web compatibility risk. Any new
methods on Array.prototype carries with it a web compat risk as many JS
libraries add their own methods to Array.prototype, and sometimes those
libraries clash with newly standardized Array.prototype.methods. Sometimes
JS Arrays are also used as hash maps, and new prototype methods clash with
existing keys used by the application. No current incompatibilities are
known or expected.


*Gecko*: Positive (https://bugzilla.mozilla.org/show_bug.cgi?id=1784092)
Stage 3 TC39 proposal. Gecko has already implemented.

*WebKit*: Positive (https://bugs.webkit.org/show_bug.cgi?id=234604) Stage 3
TC39 proposal. WebKit has already implemented.

*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?



Debuggability

Debugged as any other existing Array.prototype method


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

?In test262: see https://github.com/tc39/test262/pull/3464

Flag name--harmony-change-array-by-copy

Requires code in //chrome?False

Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=12764

Estimated milestones
DevTrial on desktop 108
DevTrial on Android 108


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

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/CAN-e9e8smpdz95tNLTkPAYWQ0OkSCMxR6_S%3Dm0ManQimtO_5uA%40mail.gmail.com.

[blink-dev] Intent to Ship: Symbols as WeakMap keys

2022-11-01 Thread &#x27;Shu-yu Guo' via blink-dev 
Contact emails...@chromium.org

Explainerhttps://github.com/tc39/proposal-symbols-as-weakmap-keys

Specificationhttps://tc39.es/proposal-symbols-as-weakmap-keys

Summary

This proposal allows Symbols to be used as keys in WeakMaps, WeakSet, as
the referent in a WeakRef, and as the target in a FinalizationRegistry.


Blink componentBlink>JavaScript>Language


TAG reviewThis is a TC39 JS language feature that doesn't have any
interaction with web APIs.

TAG review statusNot applicable

Risks


Interoperability and Compatibility



*Gecko*: Positive Stage 3 TC39 proposal

*WebKit*: Positive Stage 3 TC39 proposal

*Web developers*: No signals

*Other signals*:

WebView application risks

None?

Debuggability

This proposal adds Symbols as keys to weak collections and weak data
structures, which already exist and are debuggable. The V8 inspector was
extended [1] to support Symbols in collections. [1]
https://chromium-review.googlesource.com/c/v8/v8/+/3930037


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

?
In test262 

Flag name--harmony-symbol-as-weakmap-key

Requires code in //chrome?False

Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=12947

Estimated milestones
DevTrial on desktop 108
DevTrial on Android 108

Anticipated spec changes

None


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

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/CAN-e9e8JuO3YqLNDg2FkGWswKQOeOQVYiM3BTM-Z-jaCNfOrxg%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: Array grouping

2022-09-21 Thread Shu-yu Guo 
On Wed, Sep 21, 2022 at 8:53 AM Philip Jägenstedt 
wrote:

> I assume that like most JS features this isn't tested in WPT but rather in
> Test262. Are the tests for this in Test262 all passing?
>

Correct, it is tested via test262. I've been checking that box assuming
that it's a stand-in for test262, and listing the test262 tests in the "WPT
description" field in chromestatus. The tests in this case are located at:

   -
   
https://github.com/tc39/test262/tree/main/test/built-ins/Array/prototype/group
   -
   
https://github.com/tc39/test262/tree/main/test/built-ins/Array/prototype/groupToMap

All of the test262 tests are currently passing on V8.


>
> On Wed, Sep 21, 2022 at 12:47 PM Daniel Bratell 
> wrote:
>
>> LGTM2 to ship group and groupToMap (a bit confusing that the summary uses
>> the old names).
>>
> Thanks for pointing this out. Updated.

> /Daniel
>> On 2022-09-21 06:55, Yoav Weiss wrote:
>>
>> LGTM1
>>
>> On Wed, Sep 21, 2022 at 2:30 AM Shu-yu Guo  wrote:
>>
>>> Contact emails s...@chromium.org
>>>
>>> Explainer
>>> https://github.com/tc39/proposal-array-grouping/blob/main/README.md
>>>
>>> Specification https://tc39.es/proposal-array-grouping/
>>>
>>> Summary
>>>
>>> Adds news Array.prototype methods groupBy() and groupByToMap() to
>>> perform a grouping or bucketing operation.
>>>
>>>
>>> Blink component Blink>JavaScript>Language
>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EJavaScript%3ELanguage>
>>>
>>> TAG review
>>>
>>> TAG review status Not applicable
>>>
>>> Risks
>>>
>>>
>>> Interoperability and Compatibility
>>>
>>> Web compat risk due to Sugar. The original proposed name of
>>> Array.prototype.groupBy was found to be incompatible. See
>>> https://github.com/tc39/proposal-array-grouping/issues/37 Currently
>>> named `group` and `groupToMap` with no known incompatibilities.
>>>
>>>
>>> *Gecko*: Shipped/Shipping (
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1739648) Firefox shipped
>>> in Nightly and found a web compat issue, and are attempting outreach:
>>> https://bugzilla.mozilla.org/show_bug.cgi?id=1750812#c5 Method was
>>> renamed to `group` and `groupToMap`
>>>
>>> *WebKit*: Shipped/Shipping (
>>> https://bugs.webkit.org/show_bug.cgi?id=234327)
>>>
>>> *Web developers*: Strongly positive (
>>> https://twitter.com/rauschma/status/1470854996459769867?s=20&t=DDr_7gzapEKcfF2MbEVzHA
>>> )
>>>
>>> *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?
>>>
>>>
>>> Debuggability
>>>
>>> This feature adds two new built-in Array.prototype methods, which are
>>> debuggable like all other built-in methods.
>>>
>>>
>>> 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 --harmony-array-grouping
>>>
>>> Requires code in //chrome? False
>>>
>>> Tracking bug https://bugs.chromium.org/p/v8/issues/detail?id=12499
>>>
>>> Estimated milestones
>>> DevTrial on desktop 100
>>> DevTrial on Android 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/5714791975878656
>>>
>>> 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

[blink-dev] Intent to Ship: Array grouping

2022-09-20 Thread Shu-yu Guo 
Contact emails...@chromium.org

Explainerhttps://github.com/tc39/proposal-array-grouping/blob/main/README.md

Specificationhttps://tc39.es/proposal-array-grouping/

Summary

Adds news Array.prototype methods groupBy() and groupByToMap() to perform a
grouping or bucketing operation.


Blink componentBlink>JavaScript>Language


TAG review

TAG review statusNot applicable

Risks


Interoperability and Compatibility

Web compat risk due to Sugar. The original proposed name of
Array.prototype.groupBy was found to be incompatible. See
https://github.com/tc39/proposal-array-grouping/issues/37 Currently named
`group` and `groupToMap` with no known incompatibilities.


*Gecko*: Shipped/Shipping (
https://bugzilla.mozilla.org/show_bug.cgi?id=1739648) Firefox shipped in
Nightly and found a web compat issue, and are attempting outreach:
https://bugzilla.mozilla.org/show_bug.cgi?id=1750812#c5 Method was renamed
to `group` and `groupToMap`

*WebKit*: Shipped/Shipping (https://bugs.webkit.org/show_bug.cgi?id=234327)

*Web developers*: Strongly positive (
https://twitter.com/rauschma/status/1470854996459769867?s=20&t=DDr_7gzapEKcfF2MbEVzHA
)

*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?



Debuggability

This feature adds two new built-in Array.prototype methods, which are
debuggable like all other built-in methods.


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--harmony-array-grouping

Requires code in //chrome?False

Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=12499

Estimated milestones
DevTrial on desktop 100
DevTrial on Android 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/5714791975878656

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/CAN-e9e_OXi4njvB46nEMzTJzpoGXWEjYXEgo-7-%3DYCuT2EEeew%40mail.gmail.com.

Re: [blink-dev] Intent to Ship: Array and TypedArray findLast and findLastIndex

2021-10-08 Thread &#x27;Shu-yu Guo' via blink-dev 
Hi Joe,

I will land the flag flip early next week, which would put this
on-by-default in M97.

On Fri, Oct 8, 2021 at 7:00 AM Joe Medley  wrote:

> Shu-yu,
>
> In which version are you wanting to ship?
>
> Joe
> 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, Oct 7, 2021 at 10:22 AM 'Shu-yu Guo' via blink-dev <
> blink-dev@chromium.org> wrote:
>
>> Contact emails...@chromium.org
>>
>> Explainerhttps://github.com/tc39/proposal-array-find-from-last
>>
>> Specificationhttps://tc39.es/proposal-array-find-from-last/index.html
>>
>> Summary
>>
>> This is a Stage 3 TC39 proposal that adds the methods findLast and
>> findLastIndex to Array.prototype and the various TypedArray.prototypes.
>> These methods are the "from the end" versions of find and findIndex.
>>
>>
>> Blink componentBlink>JavaScript>Language
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EJavaScript%3ELanguage>
>>
>> TAG review
>>
>> TAG review statusNot applicable
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>> Adding any new methods to Array.prototype runs the risk of web
>> incompatibility due to breaking old libraries. Rollout will need to be
>> monitored.
>>
>>
>> Gecko: Positive This is Stage 3 in TC39
>>
>> WebKit: Positive This is Stage 3 in TC39
>>
>> Web developers: Positive (
>> https://twitter.com/mgechev/status/1432199126570131459?s=20)
>>
>>
>> Debuggability
>>
>> It is a new prototype method, so can be debugged like any other prototype
>> method.
>>
>>
>> Is this feature fully tested by web-platform-tests
>> <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md>
>> ?Yes, in test262
>>
>> Flag name--harmony-array-find-last
>>
>> Requires code in //chrome?False
>>
>> Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=11990
>>
>> Estimated milestones
>> DevTrial on desktop 94
>> DevTrial on android 94
>> DevTrial on Webview 94
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5693639729610752
>>
>> This intent message was generated by Chrome Platform Status
>> <https://www.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+unsubscr...@chromium.org.
>> To view this discussion on the web visit
>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e8M7%3DfAX%2BfwmAzEY_bngPrJPzrD4sgctRoq-7TV46tCUg%40mail.gmail.com
>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e8M7%3DfAX%2BfwmAzEY_bngPrJPzrD4sgctRoq-7TV46tCUg%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e9LwNjEA6%2B5Uio-Qj3Ypw1RykEpnZtZpX5xq8L2QmfqDA%40mail.gmail.com.

[blink-dev] Intent to Ship: Array and TypedArray findLast and findLastIndex

2021-10-07 Thread &#x27;Shu-yu Guo' via blink-dev 
Contact emails...@chromium.org

Explainerhttps://github.com/tc39/proposal-array-find-from-last

Specificationhttps://tc39.es/proposal-array-find-from-last/index.html

Summary

This is a Stage 3 TC39 proposal that adds the methods findLast and
findLastIndex to Array.prototype and the various TypedArray.prototypes.
These methods are the "from the end" versions of find and findIndex.


Blink componentBlink>JavaScript>Language


TAG review

TAG review statusNot applicable

Risks


Interoperability and Compatibility

Adding any new methods to Array.prototype runs the risk of web
incompatibility due to breaking old libraries. Rollout will need to be
monitored.


Gecko: Positive This is Stage 3 in TC39

WebKit: Positive This is Stage 3 in TC39

Web developers: Positive (
https://twitter.com/mgechev/status/1432199126570131459?s=20)


Debuggability

It is a new prototype method, so can be debugged like any other prototype
method.


Is this feature fully tested by web-platform-tests

?Yes, in test262

Flag name--harmony-array-find-last

Requires code in //chrome?False

Tracking bughttps://bugs.chromium.org/p/v8/issues/detail?id=11990

Estimated milestones
DevTrial on desktop 94
DevTrial on android 94
DevTrial on Webview 94

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

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/CAN-e9e8M7%3DfAX%2BfwmAzEY_bngPrJPzrD4sgctRoq-7TV46tCUg%40mail.gmail.com.