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 24401 - abort() should always dispatch loadend
Summary: abort() should always dispatch loadend
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: File API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Arun
QA Contact: public-webapps-bugzilla
Depends on:
Reported: 2014-01-26 20:08 UTC by Ms2ger
Modified: 2014-03-03 21:04 UTC (History)
2 users (show)

See Also:

Test Case (714 bytes, text/html)
2014-02-04 21:03 UTC, Arun

Description Ms2ger 2014-01-26 20:08:23 UTC
IE, Chrome and Firefox all dispatch loadend when you call abort() when the readyState is LOADING.
Comment 1 Anne 2014-01-29 21:30:13 UTC
Oooh, this is filed against the File API. I thought it was against XMLHttpRequest, but I already have this covered. :-)
Comment 2 Arun 2014-02-04 21:03:07 UTC
Created attachment 1435 [details]
Test Case

This test case illustrates inconsistent behavior across browsers w.r.t. FileReader.abort(), notably that toggling based on readyState is not being followed in Fx. Fixing this spec bug may also result in a Fx bug.

I'll add this test case to the Git repo for testcases as well.
Comment 3 Arun 2014-03-03 21:04:19 UTC
Fixed spec. to always fire loadend