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 23:50:50 +0000
To: public-script-coord@w3.org
Message-Id: <E1S4hg2-0005l6-Fu@jessica.w3.org>

--- Comment #10 from Cameron McCormack <cam@mcc.id.au> 2012-03-05 23:50:47 UTC ---
Whether we want all event listener attributes to use [TreatNonCallableAsNull]
or not is beside the point.  (I don't know if there is agreement either way on
that -- my own opinion is that it would be better to have all event listener
attributes behave consistently, even if only a select few needed the
[TreatNonCallableAsNull] behaviour for current web content.  If we need to
change the warning that is in the spec at the moment, that is up for

But I don't see the need to use [TreatNonCallableAsNull] anywhere else other
than event listener attributes.  For that reason, I don't think it needs to
gain first class IDL syntax.  And as we've already discussed in the other bug,
callbacks are not just for EventListener.

It is possible to define how event listener attributes work using the existing
Web IDL functionality with the typedef in comment 3; DOM Core can define this
and all specs defining event listener attributes can reference it.

*If* we wanted [TreatNonCallableAsNull] behaviour for *all* callbacks -- not
just those for event listener attributes -- then we could get rid of it and
build its behaviour into the "convert JS value to IDL callback value"
algorithm.  But I don't think that's what we want.

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 23:50:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:05 UTC