Skip to content
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

Merged
merged 1 commit into from
Mar 24, 2016
Merged

Update the ECMAScript reference #784

merged 1 commit into from
Mar 24, 2016

Conversation

annevk
Copy link
Member

@annevk annevk commented Mar 2, 2016

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.

@annevk annevk added the do not merge yet Pull request must not be merged per rationale in comment label Mar 2, 2016
@annevk
Copy link
Member Author

annevk commented Mar 2, 2016

This does not really work. See tc39/proposal-ecmascript-sharedmem#39.

@annevk
Copy link
Member Author

annevk commented Mar 24, 2016

@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
Copy link
Member

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.

Copy link
Member Author

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?

@domenic
Copy link
Member

domenic commented Mar 24, 2016

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?

@annevk annevk changed the title Support SharedArrayBuffer in StructuredCloneWithTransfer Update the ECMAScript reference Mar 24, 2016
Also reference https://javascript.spec.whatwg.org/ normatively for as
long as it’s still relevant and require it to be implemented.
@annevk
Copy link
Member Author

annevk commented Mar 24, 2016

Done.

@domenic
Copy link
Member

domenic commented Mar 24, 2016

LGTM

@annevk annevk merged commit fedaaea into master Mar 24, 2016
@annevk annevk deleted the sab branch March 24, 2016 15:43
@annevk annevk added clarification Standard could be clearer and removed do not merge yet Pull request must not be merged per rationale in comment labels Mar 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
clarification Standard could be clearer
Development

Successfully merging this pull request may close these issues.

2 participants