W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2011

[Bug 13997] New: Require that attributes are exposed on the interface prototype object

From: <bugzilla@jessica.w3.org>
Date: Thu, 01 Sep 2011 15:24:51 +0000
To: public-script-coord@w3.org
Message-ID: <bug-13997-3890@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13997

           Summary: Require that attributes are exposed on the interface
                    prototype object
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebIDL
        AssignedTo: cam@mcc.id.au
        ReportedBy: simonp@opera.com
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-script-coord@w3.org


http://dev.w3.org/2006/webapi/WebIDL/#es-attributes says

[[
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
or on every object that implements the interface.
]]

Why does it say "or on every object that implements the interface"? That leaves
a choice for the implementor and leads to interop problems and harder object
detection for authors. It would be better if it required the attributes to be
exposed on the interface prototype object.

See http://www.w3.org/Bugs/Public/show_bug.cgi?id=13984 for a case where this
causes problems.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 1 September 2011 15:24:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:04 UTC