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.
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.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
Debugged as any other existing Array.prototype method
DevTrial on desktop | 108 |
DevTrial on Android | 108 |
LGTM1
/Daniel
--
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+...@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.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/60b4b6df-7569-68d0-5e5f-bd425ffa90e6%40gmail.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAARdPYckRz39nKfFQmfFnmxErfWeFTr4yQsXaZiYVdE8UCj%3DCg%40mail.gmail.com.