Contact emailsrez...@chromium.org, s...@chromium.org

ExplainerNone

Specificationhttps://tc39.es/proposal-arraybuffer-base64/spec

Summary

base64 is a common way to represent arbitrary binary data as ASCII.
JavaScript has Uint8Arrays to work with binary data, but no built-in
mechanism to encode that data as base64, nor to take base64'd data and
produce a corresponding Uint8Arrays. This is a proposal to fix that. It
also adds methods for converting between hex strings and Uint8Arrays.


Blink componentBlink>JavaScript>Language
<https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EJavaScript%3ELanguage%22>

TAG reviewNone

TAG review statusNot applicable

Risks


Interoperability and Compatibility

None


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

*WebKit*: Shipped/Shipping (
https://webkit.org/blog/15798/release-notes-for-safari-technology-preview-202
) https://bugs.webkit.org/show_bug.cgi?id=274635
https://bugs.webkit.org/show_bug.cgi?id=276215
https://bugs.webkit.org/show_bug.cgi?id=275593

*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

It is debugged as any other static method in JavaScript.


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

https://github.com/tc39/test262/pull/3994


Flag name on about://flags--js_base_64

Finch feature nameV8Flag_js_base_64

Rollout planWill ship enabled for all users

Requires code in //chrome?False

Estimated milestones
Shipping on desktop 140
DevTrial on desktop 138
Shipping on Android 140
DevTrial on Android 138

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/6281131254874112?gate=5080623806676992

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 visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CACJ3t%2BiV8C-08B%2BPgWMbthK5MrdjV%2BO71%2Bq5%3D2rhVF5AKkSXAw%40mail.gmail.com.

Reply via email to