- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 Jul 2012 19:27:01 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17236
Jonas Sicking <jonas@sicking.cc> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jonas@sicking.cc
--- Comment #3 from Jonas Sicking <jonas@sicking.cc> 2012-07-12 19:27:00 UTC ---
Hmm.. I think it would be good to avoid throwing for this property.
Right now accessing the .error property is the only way to check if a
transaction has been aborted (though it's not perfect since if you manually
abort a transaction then it'll remain null).
For request.error it's pretty easy to avoid accessing
request.error/request.result by simply waiting for the success/error event to
fire.
On a transaction this might be more tricky since you might in the error event
from a request know if the transaction has been aborted or not, to avoid
placing more requests against it.
Right now the only way to do that is to check transaction.error
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 12 July 2012 19:27:03 UTC