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 25138 - "Invoking callback functions"
Summary: "Invoking callback functions"
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
Depends on:
Blocks: 17713
  Show dependency treegraph
Reported: 2014-03-24 16:39 UTC by Anne
Modified: 2016-06-02 20:49 UTC (History)
4 users (show)

See Also:


Description Anne 2014-03-24 16:39:20 UTC

Invoking callback functions

I feel like we want this to be a <dfn> thing that we can cross-reference. That way it is more clear when a specification does not define what to do with a callback that throws.
Comment 1 Anne 2014-03-24 16:40:27 UTC
Or we should have this as a lower-level hook and then a higher-level hook that is "invoke and report" as Ian just suggested on IRC. That higher-level hook should maybe be in HTML?
Comment 2 Ian 'Hixie' Hickson 2014-03-24 16:50:11 UTC
Happy to add something that invokes a callback and then catches and reports exceptions. Assign this bug to me when "invoking callback functions" is ready, or file a new bug on me?
Comment 3 Anne 2014-11-26 10:30:18 UTC
Note: bug 27046 added the "report the exception" algorithm which reports an exception to window.onerror.
Comment 4 Domenic Denicola 2016-06-02 20:49:16 UTC
A plan for the exception-handling behavior was discussed in and is tracked at The original request for a <dfn> was fixed in