[Bug 19470] Event firing sequence on abort() after send() from bugzilla@jessica.w3.org on 2013-02-19 (public-webapps-bugzilla@w3.org from February 2013)

From: <bugzilla@jessica.w3.org>
Date: Tue, 19 Feb 2013 16:02:58 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-19470-2532-ZV5N9ESn82@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19470

--- Comment #8 from Anne <annevk@annevk.nl> ---
So actually Dominik, I think what Gecko does, given comment 0 is correct, is
correct. Invoking abort() should not change events dispatched as part of the
same task, I think. If you invoke abort() when fetching is done (as this.DONE
indicates) you're simply too late.

What I fixed in the specification is the ambiguity we had before.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 19 February 2013 16:03:03 UTC