RESOLVED CONFIGURATION CHANGED 76107
WebKit fails IETC Override_Property_Setter_High (both JSC and V8)
https://bugs.webkit.org/show_bug.cgi?id=76107
Summary WebKit fails IETC Override_Property_Setter_High (both JSC and V8)
Eric Seidel (no email)
Reported 2012-01-11 14:55:10 PST
WebKit fails IETC Override_Property_Setter_High (both JSC and V8) http://samples.msdn.microsoft.com/ietestcenter/dominheritance/showdominheritancetest.htm?Override_Property_Setter_High Passes in FF. There seem to be a number of Object.defineProperty bugs on file, maybe this is just a dupe of one of them. The test is doing the following: var setValue = false; if (Object.defineProperty) { Object.defineProperty(Node.prototype, "nodeName", { set: function () { setValue = true; } }); } var div = document.createElement("div"); div.nodeName = "foo"; if (setValue) { document.getElementById("testresult").innerHTML = "Pass"; } CCing the JavaScript ninjas. See also bug 76106 which is about the "getter" variant of this test.
Attachments
Geoffrey Garen
Comment 1 2012-01-11 15:21:20 PST
I think this is really a test of the DOM API. Whether a setter on the prototype overrides the DOM API depends on whether the DOM API is expressed as a setter on the DOM object's prototype or a direct property on the DOM object.
Zan Dobersek
Comment 2 2012-12-17 08:26:57 PST
I guess this boils down to the differences between WebKitIDL and WebIDL, as explained here: http://trac.webkit.org/wiki/WebKitIDL#V8Unforgeable
Zan Dobersek
Comment 3 2012-12-17 08:30:50 PST
This bug and bug #76106 should probably be marked as a duplicate of bug #49739 as many other bugs have been before.
Ahmad Saleem
Comment 4 2024-02-03 14:06:04 PST
@Alexey - is this applicable anymore?
Alexey Shvayka
Comment 5 2024-02-04 13:17:03 PST
(In reply to Eric Seidel (no email) from comment #0) > WebKit fails IETC Override_Property_Setter_High (both JSC and V8) > > http://samples.msdn.microsoft.com/ietestcenter/dominheritance/ > showdominheritancetest.htm?Override_Property_Setter_High The link is no longer alive yet we pass the inline test case since bindings redesign circa 2015. Redefinition of DOM properties is heavily covered by both WPT and our tests.
Note You need to log in before you can comment on or make changes to this bug.