Re: [w3c/IndexedDB] Disallow starting readwrite transactions while readonly transactions are running? (#253)

> Anyone relying on it would have cross-browser bugs

How so? Is that based on the assumption that people are relying on the ordering of transactions? Like @pwnall is describing, I did not know I _could_ rely on the order, nor would I (if and when I'd need it, I would handle such a thing in the application).

> We'll be monitoring metrics to see if it affects performance of sites in a measurable way.

IMO IndexedDB has never been optimal for large amounts of data (with backpressure), which means you'll have a "blind spot" in the spectrum of use cases. If no one uses IndexedDB like that (because they can't, not because they don't want to) then metrics will not show a performance degradation. 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/253#issuecomment-455682700