Feross on Twitter: "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: https://t.co/I61x27obtv cc @webkit @chris_dumez @Apple"
Founder of Socket (http:// socket.dev ) • Mad scientist • Stanford lecturer • @Wormhole_App (http:// wormhole.app ) • Open sourcerer at @WebTorrentApp and @StandardJS
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
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: https:// bugs.webkit.org/show_bug.cgi?i d=226547 … 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 ` http:// indexedDB.open ()` will succeed. If I had to guess, Safari is lazily opening the DB in another process but somehow doing it wrong.
.png)
