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 25210 - Targets for abort event is correct?
Summary: Targets for abort event is correct?
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Gary Kacmarcik
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-31 01:34 UTC by Arkadiusz Michalski (Spirit)
Modified: 2014-04-29 00:27 UTC (History)
3 users (show)

See Also:

Attachments

Description Arkadiusz Michalski (Spirit) 2014-03-31 01:34:52 UTC 
Why in table for abort: https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#event-type-abort

we have only Element as target? 

In HTML5 this event is dispatch to:

- Element, like audio/video (http://www.w3.org/html/wg/drafts/html/master/embedded-content.html#fatal-decode-error), maybe for img too, but I can not specify the algorithm for img.

- window object (http://www.w3.org/html/wg/drafts/html/master/index.html#event-abort). Algorithm http://www.w3.org/html/wg/drafts/html/master/browsers.html#abort-a-document.

And event handler onabort can be used for Element, Document and Window, so we can catch this event from all possibility (http://www.w3.org/html/wg/drafts/html/master/webappapis.html#event-handlers-on-elements,-document-objects,-and-window-objects). 

I think minimum should be defaultView and Element (maybe Document too).
Comment 1 Travis Leithead [MSFT] 2014-04-23 00:41:29 UTC 
Excellent. Thanks for the research. I'll see about extending this...
Comment 2 Travis Leithead [MSFT] 2014-04-28 23:37:21 UTC 
... Gary is making this change with a bit table update...
Comment 3 Travis Leithead [MSFT] 2014-04-29 00:27:27 UTC 
Fixed by https://dvcs.w3.org/hg/dom3events/rev/40019b0b87c3