978924 - FileAPI Abort Call Fires Wrong Event Order, with Accompanying Wrong FileReader State

Status: RESOLVED WORKSFORME

(Core :: DOM: Core & HTML, defect)

Description

[Arun Ranganathan]

Attachment: abortTester.html - Demo of the abort call

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:27.0) Gecko/20100101 Firefox/27.0

Steps to reproduce:

The attached HTML file invokes FileReader.abort() on a given FileReader. 

Actual Result:

"abort 2"
"loadend 2" 
"loadstart 2"

Expected Result:

"loadstart 1" 
"abort 2" 
"loadend 2"

Explanation:

When loadstart fires, the state should be LOADING.
The 'abort' event fires and the state of the FileReader should be DONE.
The 'loadend' event fires and the state of the FileReader should be DONE. 

Also, the Fx event firing sequence is illogical.

Comment 1

[:Ms2ger (he/him; ⌚ UTC+1/+2)]

This is a direct result of your spec defining that abort() fires its event synchronously, and your test logging "loadstart" after calling abort(). See $URL for a better test.

Comment 2

[Arun Ranganathan]

I'm not sure you should close this bug. It still shows event inconsistency w.r.t Chrome. Also, the spec. has changed (to always fire loadend).