Issue 3080018: According to ES-262, Object.seal and Object.freeze should return object's its...

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 3080018: According to ES-262, Object.seal and Object.freeze should return object's its... (Closed)

Created:
10 years, 4 months ago by burcu

Modified:
9 years, 7 months ago

Reviewers:
Søren Thygesen Gjesse

CC:
v8-dev

Base URL:
http://v8.googlecode.com/svn/trunk/

Visibility:
Public.

Description

According to ES-262, Object.seal and Object.freeze should return object's itself after the modifications. BUG=809 TEST=Seal and freeze a blank {} object and make sure that returning output's type is not undefined

Patch Set 1 #

Created: 10 years, 4 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+3 lines, -3 lines)			Patch
	M	AUTHORS	View		1 chunk	+1 line, -1 line	0 comments	Download
	M	src/v8natives.js	View		2 chunks	+2 lines, -2 lines	0 comments	Download

Messages

Total messages: 1 (0 generated)

Expand Messages | Collapse Messages

Søren Thygesen Gjesse

10 years, 4 months ago (2010-08-03 08:38:57 UTC) #1

Thanks for the patch, could you please add tests to the mjsunit tests:

  test/mjsunit/object-freeze.js
  test/mjsunit/object-seal.js

Is this issue caught by any of the ES5 conformance tests?

Expand Messages | Collapse Messages