On 6/7/11 5:04 PM, Jonas Sicking wrote:
On Tue, Jun 7, 2011 at 11:51 AM, Jian Li<jia...@chromium.org>  wrote:

On Tue, Jun 7, 2011 at 11:23 AM, Jonas Sicking<jo...@sicking.cc>  wrote:
On Tue, Jun 7, 2011 at 10:43 AM, Jian Li<jia...@chromium.org>  wrote:
I have a couple questions regarding abort behavior.

If the reading is completed and the loadend event has been fired, do we
want
to fire loadend event again when abort() method is called?
No

Do we want to reset error to null or leave it intact when abort() method
is
called?
If called after load/abort/error has fired the calling abort() should
just throw an exception and not alter the FileReader object in any
way.
Do you mean we should throw if abort() is called after load/abort/error has
been fired but before loadend event has been fired?
Yes.

If so, what kind of exception should we throw?
I need to get updated on the status on various exceptions, so I don't
have an opinion on this at this time.

The spec only mentions that "If readyState = DONE set result to null."
I actually disagree with that sentence.

So I'm not exactly sure we should throw here. Why do you disagree? Have you revisited this opinion? What should the behavior be?


-- A*

/ Jonas


Reply via email to