LGTM1 On Thu, Mar 30, 2023 at 1:47 AM Shu-yu Guo <[email protected]> wrote:
> Contact [email protected] > > 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 > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EJavaScript%3ELanguage> > > 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 > <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> > ?In test262, see tests/built-ins/ArrayBuffer/prototype/ > <https://github.com/tc39/test262/tree/main/test/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 > <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 on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e-3%2BZpiD0ANVJFE7nKNO66Hr-aP6LgtwrjHEpcWrzmL2Q%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAN-e9e-3%2BZpiD0ANVJFE7nKNO66Hr-aP6LgtwrjHEpcWrzmL2Q%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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfUAOUqgxkPM68sCgvtsh9v0Un35mnA-Cwqpz7cHS3OZUA%40mail.gmail.com.
