Tests now run flawlessly on both Firefox and Chrome

It seems Chrome really wants us to use the transaction.oncomplete callbacks instead of request.success callbacks. Tested with both recent Firefox and Chrome versions, and test then run fine. Using the request.success callbacks on Chrome on write requests leads to indeterministic behaviour (probably related to subsequent reads being done before writes have been completed and commited to the database).