/ecma262

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

`new ArrayBuffer()` throws per spec, but not in browsers #292

Closed
ljharb opened this Issue Jan 16, 2016 · 2 comments

Comments

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@ljharb @zloirock
@ljharb
Member

ljharb commented Jan 16, 2016

Per Microsoft/ChakraCore#105 (comment) - new ArrayBuffer should throw a RangeError because SameValueZero(ToNumber(undefined), ToLength(NaN)) is false.

However, Safari, Firefox, Chrome, and Edge all return an ArrayBuffer with a byteLength of zero (same with new ArrayBuffer(NaN) and new ArrayBuffer(undefined).

Is it possible that step 4 of https://tc39.github.io/ecma262/#sec-arraybuffer-constructor is web-incompatible, and will need to be changed?

@obastemur obastemur referenced this issue Jan 16, 2016

Closed

Fix: new ArrayBuffer(Infinity) should throw RangeError #131

@zloirock

This comment has been minimized.

Show comment
Hide comment
@zloirock

zloirock Jan 16, 2016

Duplicate #265

zloirock commented Jan 16, 2016

Duplicate #265
@ljharb

This comment has been minimized.

Show comment
Hide comment
@ljharb

ljharb Jan 16, 2016

Member

oops, thanks
Member

ljharb commented Jan 16, 2016

oops, thanks

@ljharb ljharb closed this Jan 16, 2016

@agarwal-sandeep agarwal-sandeep referenced this issue Mar 18, 2016

Merged

Update node-chakracore with nodejs/master changes #40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment