Ran into a spectacularly awful Safari bug in the latest Safari (14.1.1 on macOS and iOS 14.6).
Opening an IndexedDB database fails 100% of the time on the first try. 😩
If you refresh, it starts working.
Bug report: bugs.webkit.org/show_bug.cgi?i…
cc @webkit @chris_dumez @Apple
Opening an IndexedDB database fails 100% of the time on the first try. 😩
If you refresh, it starts working.
Bug report: bugs.webkit.org/show_bug.cgi?i…
cc @webkit @chris_dumez @Apple
One workaround we've found is to reference the indexedDB global early on, like this:
const idb = globalThis.indexedDB
Then later calls to `indexedDB.open()` will succeed.
If I had to guess, Safari is lazily opening the DB in another process but somehow doing it wrong.
const idb = globalThis.indexedDB
Then later calls to `indexedDB.open()` will succeed.
If I had to guess, Safari is lazily opening the DB in another process but somehow doing it wrong.
It's really really hard to build reliable websites on macOS and iOS with showstopper bugs like this.
This should have been caught by basic unit testing.
@webkit Please prioritize this bug and release a hotfix.
This should have been caught by basic unit testing.
@webkit Please prioritize this bug and release a hotfix.
Btw, we added a workaround in Wormhole.app – so Safari users should be good to go for now :)
• • •
Missing some Tweet in this thread? You can try to
force a refresh
