[Webkit-unassigned] [Bug 70929] New: Most DOM attributes should be on the corresponding interface prototype

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Oct 26 08:34:03 PDT 2011


https://bugs.webkit.org/show_bug.cgi?id=70929

           Summary: Most DOM attributes should be on the corresponding
                    interface prototype
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: andy at intelligroup.eu


Section 4.5.5 of the Web IDL, http://www.w3.org/TR/WebIDL/#es-attributes, states that 

    "For each attribute defined on the interface, there must exist 
     a corresponding property. If the attribute was declared with 
     the [Unforgeable] extended attribute, then the property exists 
     on every object that implements the interface. Otherwise, it 
     exists on the interface’s interface prototype object."

WebKit, however, appears to define these as instance properties.  This introduces several incompatibilities, such as checking own properties or getting property descriptors.  For a specific example, In WebKit and Presto:

    > document.body.hasOwnProperty("style")
    // -> true

In Trident and Gecko:

    > document.body.hasOwnProperty("style")
    // -> 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