Bug 76148 - Allow accessor get/set property to be set to undefined
Summary: Allow accessor get/set property to be set to undefined
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
Depends on:
Reported: 2012-01-11 22:59 PST by Gavin Barraclough
Modified: 2012-01-12 10:38 PST (History)
0 users

See Also:

Fix (27.10 KB, patch)
2012-01-12 00:26 PST, Gavin Barraclough
oliver: review+
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Gavin Barraclough 2012-01-11 22:59:41 PST
AccessorDescriptor properties may have their get & set properties defined to reference a function (Callable object) or, or be set to undefined.  Valid PropertyDescriptors created by toPropertyDescriptor (defined from JS code via Object.defineProperty, etc) have get and set properties that are in one of three states (1) nonexistent (c++ null  JSValue), (2) JS undefined, or (3) a function (or any Callable).
Comment 1 Gavin Barraclough 2012-01-12 00:26:29 PST
Created attachment 122178 [details]
Comment 2 Gavin Barraclough 2012-01-12 10:38:42 PST
Fixed in r104836