This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13997 - Require that attributes are exposed on the interface prototype object
Summary: Require that attributes are exposed on the interface prototype object
Status: CLOSED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-01 15:24 UTC by Simon Pieters
Modified: 2011-09-02 06:25 UTC (History)
2 users (show)

See Also:


Attachments

Description Simon Pieters 2011-09-01 15:24:50 UTC
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.
Comment 1 Cameron McCormack 2011-09-02 04:36:47 UTC
Sorry, (as I mentioned in a private mail to you before I saw this bug) this is just a mis-edit in response to Geoffrey's comment about that paragraph of text.  This is fixed now.
Comment 2 Simon Pieters 2011-09-02 06:25:31 UTC
Thanks!