[Webkit-unassigned] [Bug 34639] Object.defineProperty accepts wrong descriptor

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Thu Feb 3 07:51:48 PST 2011


Rico <ricow at google.com> changed:

           What    |Removed                     |Added
                 CC|                            |ager at chromium.org,
                   |                            |ricow at google.com

--- Comment #8 from Rico <ricow at google.com>  2011-02-03 07:51:48 PST ---

Any updates on this?

The thread you started on es-discuss was actually discussing another issue (what the outcome should be of): 
Object.defineProperty({}, 'foo', {get:undefined})
Which is also very relevant since this is also a place where the Chrome implementation differs from Safari (Safari will make this a data property).

The original suggestion/question is still valid, since the spec is pretty clear on what should happen when ToPropertyDescriptor is called from Object.defineProperty with the following:
Object.defineProperty({}, 'foo', {get:undefined, value:42})

Step 9a says that in the case where Get or Set is present (but potentially undefined as in our case) and either writable or value is also present we should throw an error (and not define any property at all).


Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list