The changes of proposal’s status @ 104th meeting of Ecma TC39 ECMA-262 New Proposals Proposal Stage Immutable ArrayBuffers 1 Array.zip and Array.zipKeyed 1 Updated Proposals Proposal From To Promise.try 3 4 Import Attributes 3 4 RegExp Modifiers 3 4 Sync Iterator helpers 3 4 JSON Modules 3 4 Atomics.pause 2.7 3 Error.isError 2 2.7 Iterator Sequencing 2 2.7 Extractors 1 2 Structs: Fixed Layout Obje
This proposal is an early design sketch by the Chrome built-in AI team to describe the problem below and solicit feedback on the proposed solution. It has not been approved to ship in Chrome. Browsers are increasingly offering language translation to their users. Such translation capabilities can also be useful to web developers. This is especially the case when browser's built-in translation abil
The changes of proposal’s status @ 101st meeting of Ecma TC39 ECMA-262 New Proposals Proposal Stage Signals 1 Strict Enforcement of ‘using’ 1 Updated Proposals Proposal From To Dynamic Code Brand Checks 1 3 Math.sumPrecise 1 2.7 Redeclarable global eval-introduced vars 2 3 Error.isError -1 1 Promise.try 2 2.7 New Set methods 3 4 Duplicate named capture groups 3 4 ECMA-402 New Proposals No Data Upd
// binding patterns const Foo(y) = x; // instance-array destructuring const Foo([y]) = x; // nested array destructuring const Foo({y}) = x; // nested object destructuring const [Foo(y)] = x; // nesting const { z: Foo(y) } = x; // .. const Foo(Bar(y)) = x; // .. const X.Foo(y) = x; // qualified names (i.e., a.b.c) // assignment patterns Foo(y) = x; // instance-array destructuring Foo([y]) = x; // n
Accurate storage and processing of base-10 decimal numbers is a frequent need in JavaScript. Currently, developers sometimes represent these using libraries for this purpose, or sometimes use Strings. Sadly, JavaScript Numbers are also sometimes used, leading to real, end-user-visible rounding errors. What’s the issue? Why aren’t JS Numbers good enough? In what sense are they not “exact”? How is i
Stage 1 (explanation) TC39 proposal champions: Daniel Ehrenberg, Yehuda Katz, Jatin Ramanathan, Shay Lewis, Kristen Hewell Garrett, Dominic Gannaway, Preston Sego, Milo M, Rob Eisenberg Original authors: Rob Eisenberg and Daniel Ehrenberg This document describes an early common direction for signals in JavaScript, similar to the Promises/A+ effort which preceded the Promises standardized by TC39 i
Device Bound Session Credentials (DBSC) aims to reduce account hijacking caused by cookie theft. It does so by introducing a protocol and browser infrastructure to maintain and prove possession of a cryptographic key. The main challenge with cookies as an authentication mechanism is that they only lend themselves to bearer-token schemes. On desktop operating systems, application isolation is lacki
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Pick a username Email Address Password Sign up for GitHub By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails. Already on GitHub? Sign in to your account
The changes of proposal’s status @ 100th meeting of Ecma TC39 ECMA-262 New Proposals Proposal Stage ESM Phase Imports 1 Redeclarable global eval-introduced vars 2 Micro and mini waits 1 iterator chunking 1 Iterator unique 1 Improved Escapes for Template Literals 1 Function and Object Literal Decorators 1 “Discard” (void) Bindings 1 Updated Proposals 🆕 Stage 2.7 is introduced in add a new testing
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く