- From: <bugzilla@jessica.w3.org>
- Date: Thu, 12 Jul 2012 19:42:54 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=17236 --- Comment #5 from Jonas Sicking <jonas@sicking.cc> 2012-07-12 19:42:54 UTC --- I definitely think we need to set transaction.error to a non-null value even when a transaction is aborted for reasons unrelated to a request. Setting transaction.error to a non-null value is the only way the page can know why the transaction was aborted in that case. I.e. if it was due to IO errors, or due to quota errors. -- 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:42:55 UTC