Re: [w3c/IndexedDB] Cursor property updating precedes success event (#340)

> Chrome doesn't implement it this way - properties are not visible on the IDBCursor until the event fires. They're applied synchronously just before the event is dispatched.

This is also how Firefox works.  (And it's hard to imagine an implementation that operates using tasks not working this way.)

-- 
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/340#issuecomment-654470121