[Webkit-unassigned] [Bug 70207] New: After deleting __defineSetter__, it is absent but appears in name list
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Sun Oct 16 18:20:29 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=70207
Summary: After deleting __defineSetter__, it is absent but
appears in name list
Product: WebKit
Version: 528+ (Nightly build)
Platform: Macintosh Intel
OS/Version: Mac OS X 10.5
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: JavaScriptCore
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: erights at gmail.com
Below I delete __defineSetter__ on Object.prototype. Afterwards, it reappears on the end of the list returned by Object.getOwnPropertyNames but otherwise appears to be truly deleted.
This is a new problem, in that Safari Version 5.0.6 (5533.22.3) instead has the problem described by issue 61014, namely that delete reports that it successfully deleted __defineSetter__, but it seems to still be there in all the ways tested below. So is this a new bug introduced in trying to fix issue 61014 ?
> var gopn = Object.getOwnPropertyNames
> var gopd = Object.getOwnPropertyDescriptor
> gopn(Object.prototype)
constructor,__defineSetter__,valueOf,__lookupGetter__,toLocaleString,__defineGetter__,hasOwnProperty,propertyIsEnumerable,toString,__lookupSetter__,isPrototypeOf
> var desc = gopd(Object.prototype, '__defineSetter__')
> JSON.stringify(desc)
{"writable":true,"enumerable":false,"configurable":true}
> desc.value
function __defineSetter__() {
[native code]
}
> delete Object.prototype.__defineSetter__;
true
> gopn(Object.prototype)
constructor,toString,valueOf,__lookupGetter__,toLocaleString,__defineGetter__,hasOwnProperty,propertyIsEnumerable,__lookupSetter__,isPrototypeOf,__defineSetter__
> var desc = gopd(Object.prototype, '__defineSetter__')
> desc === undefined
true
> Object.prototype.__defineSetter__ === undefined
true
> '__defineSetter__' in Object.prototype
false
--
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