W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > November 2011

[Bug 13252] possible inconsistent exposure of event attributes

From: <bugzilla@jessica.w3.org>
Date: Sun, 20 Nov 2011 18:52:35 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1RSCVH-0005qs-Ut@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=13252

Glenn Adams <glenn@skynav.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NEEDSINFO                   |

--- Comment #3 from Glenn Adams <glenn@skynav.com> 2011-11-20 18:52:35 UTC ---
The intent of this bug report is to point out an asymmetry between expressing
event handlers declaratively (as content attributes) and procedurally (as IDL
attributes).

With the exception of the event handlers listed in this bug, all event handlers
can be expressed either declaratively or procedurally.

In order to improve interoperability (and reduce exceptional conditions for
authors), I recommend that content attributes be added (to their respective
elements) for each of the event handlers listed here.

For example, the event handlers defined on ApplicationCache could be exposed as
content attributes on the html element (where the manifest attribute would be
expressed) or on the body element.

If the decision is not to add corresponding content attributes, then it would
be useful to express somewhere in the spec that not all event handlers have
both content attribute and IDL attribute definitions.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 20 November 2011 18:52:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 20 November 2011 18:52:43 GMT