Bug 76107 - WebKit fails IETC Override_Property_Setter_High (both JSC and V8)
Summary: WebKit fails IETC Override_Property_Setter_High (both JSC and V8)
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 76198
  Show dependency treegraph
 
Reported: 2012-01-11 14:55 PST by Eric Seidel (no email)
Modified: 2012-12-17 08:30 PST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eric Seidel (no email) 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.
Comment 1 Geoffrey Garen 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.
Comment 2 Zan Dobersek 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
Comment 3 Zan Dobersek 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.