Ran into a spectacularly awful Safari bug in the latest Safari (14.1.1 on macOS and iOS 14.6).— Feross (@feross) June 14, 2021
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
But, ok, that’s fine, we were refactoring the app and saving less state in browser storage, and we were going to use localStorage instead because cross-tab communication is easier but haha fuck me right?
😬 localStorage is broken in Safari 14.1.— Jake Archibald (@jaffathecake) May 4, 2021
Tabs end up with seperate localStorage for reading, but the same localStorage for writing. This will likely result in data loss for users. (h/t @forresto)https://t.co/5Ljxl4vvbH
I use Safari on a day to day basis because it is fast, but also because there’s no better way to find out what dumb things are broken in Safari that will break your app than seeing it broken in someone else’s app. Oh and forget Google Lighthouse, you want to know if an app is good just open it in Safari and see if you get the “this page is consuming significant energy” warning.
This used up exactly all of the material, and the grass there is now pleasingly geometric so we’re done with that part of the yard.
Comments? Questions? Just want to say hi? Get in touch.