This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/ Multipage: http://www.whatwg.org/C#timers Complete: http://www.whatwg.org/c#timers Referrer: Comment: "Call the Function. Use the third and subsequent method arguments (if any) as the arguments for invoking the Function. Use method context proxy as the thisArg for invoking the Function." — we should instead stash away the callback and use WebIDL's "invoke a callback" logic. Posted from: 2620:0:1000:167c:70ad:5201:ebd7:23de by ian@hixie.ch User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/32.0.1685.0 Safari/537.36
heycam, can you point me to the right place in WebIDL for this?
Note to self: I need to change "In this step, invoke means to run the jump to a code entry-point algorithm." in the event handler section to call into WebIDL as well, in case someone sets an event handler to a non-script.
*** Bug 19211 has been marked as a duplicate of this bug. ***
Note to self: see bug 19211 for other things to change.
This is currently blocked on getting changes to ES6. See: http://esdiscuss.org/topic/the-initialization-steps-for-web-browsers#content-32
https://bugs.ecmascript.org/show_bug.cgi?id=3139 "post ES6"
I got tired of waiting for ES to be fixed, so I've updated event handlers to call Web IDL, and we'll fix the parsing of event handlers when ES catches up.
Checked in as WHATWG revision r8880. Check-in comment: Fix callback logic to reference Web IDL and use the right conventions. https://html5.org/tools/web-apps-tracker?from=8879&to=8880