- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 Jul 2012 19:20:05 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17236 --- Comment #2 from Jonas Sicking <jonas@sicking.cc> 2012-07-12 19:20:04 UTC --- Spec definitely has wrong text here. The behavior I think we should have is the one I believe I detailed in my proposal around error handling to the list a while ago (and which received general agreement). Basically: transaction.error returns null when a transaction is created (i.e. accessing transaction.error does not throw, unlike request.error). If a request fails, transaction.error remains null while firing the error event on the request, and while that error event bubbles to the to the transaction and the database. If the event isn't preventDefault'ed, transaction.error is set to the appropriate, non-null, error and an "abort" event is fired on the transaction. -- 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:20:07 UTC