-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Update the ECMAScript reference #784
Conversation
This does not really work. See tc39/proposal-ecmascript-sharedmem#39. |
@domenic what do you think about landing the first commit here? I don't think we should do the second commit without the serialize as records, deserialize from record rewrite. |
|
||
<p class="note">The term "JavaScript" is used to refer to ECMA262, rather than the official term | ||
ECMAScript, since the term JavaScript is more widely known. Similarly, the <span>MIME | ||
<p class="note">The term "JavaScript" is used to refer to JAVASCRIPT, rather than the official |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this probably shouldn't be changed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yes, I should change ECMA262 to ECMA-262, right?
First commit seems good with a nit. Should we also add a sentence explicitly about how user agents must follow the additions and clarifications in the WHATWG JavaScript standard? |
Also reference https://javascript.spec.whatwg.org/ normatively for as long as it’s still relevant and require it to be implemented.
Done. |
LGTM |
This used to be a PR for SharedArrayBuffer support, see #935 for #936, tc39/proposal-ecmascript-sharedmem#65, and tc39/proposal-ecmascript-sharedmem#39 for that instead.
Now this is a PR for updating the ECMAScript reference situation in HTML.