W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2012

[Bug 16074] Define |[TreatNonCallableAsNull] Function?| as a builtin

From: <bugzilla@jessica.w3.org>
Date: Mon, 05 Mar 2012 18:03:30 +0000
To: public-script-coord@w3.org
Message-Id: <E1S4cFu-0008VU-SN@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16074

--- Comment #9 from Marcos Caceres <w3c@marcosc.com> 2012-03-05 18:03:30 UTC ---
My objection is that recommending avoiding the use of [TreatNonCallableAsNull]
makes event handlers in new specs behave in a way that is different from other
specs (e.g., HTML5's on*). This is confusing in that it means some event
handlers behave one way, and other (new ones) in another way... I am not the
best to judge, but I kinda like the behavior of [TreatNonCallableAsNull]. 

Having said that, I would be strongly in favor of having a general mechanism
for defining "event handler IDL attributes".

-- 
Configure bugmail: https://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 Monday, 5 March 2012 18:03:32 UTC

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