LGTM1
On 8/24/26 9:40 a.m., Chromestatus wrote:
*Contact emails*
[email protected], [email protected]
*Explainer*
https://github.com/tc39/proposal-iterator-includes
*Specification*
https://tc39.es/proposal-iterator-includes
*Summary*
A TC39 proposal to allow the developer to ask whether an iterator
yields a given value. Analogue to `Array.prototype.includes`.
*Blink component*
Blink>JavaScript>Language
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EJavaScript%3ELanguage%22>
*Web Feature ID*
tc39-iterator-includes
<https://webstatus.dev/features/tc39-iterator-includes>
*Motivation*
/No information provided/
*Initial public proposal*
/No information provided/
*TAG review*
/No information provided/
*TAG review status*
Not applicable
*Goals for experimentation*
None
*Risks*
*Interoperability and Compatibility*
/No information provided/
/Gecko/:
Shipped/Shipping (https://bugzilla.mozilla.org/show_bug.cgi?id=2025773)
/WebKit/: In development (https://bugs.webkit.org/show_bug.cgi?id=310698)
/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?
/No information provided/
*Debuggability*
/No information provided/
*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
Covered by Test262
*Flag name on about://flags*
/No information provided/
*Finch feature name*
V8Flag_js_iterator_includes
*Rollout plan*
Will ship enabled for all users
*Requires code in //chrome?*
False
*Tracking bug*
https://issues.chromium.org/issues/504886973
*Estimated milestones*
Shipping on desktop 154
Shipping on Android 154
Shipping on WebView 154
*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).
/No information provided/
*Link to entry on the Chrome Platform Status*
https://chromestatus.com/feature/5205192866922496?gate=6089497379995648
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 [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a8c49ea.f0bac957.7b6f1.0987.GAE%40google.com
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a8c49ea.f0bac957.7b6f1.0987.GAE%40google.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 [email protected].
To view this discussion visit
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/2673b86b-0970-4a73-be2a-1b8b1b211c30%40chromium.org.
