4 ms·

The IndexedDB API in Safari has been buggy and unstable for a very long time.

• gwill 5y ago
  new bugs all the time too. in iOS 13 i found a bug where getting data from a store by key would ignore whatever store you pass it, so it would return data from every store that matched the key.
• mrweasel 5y ago
  Given that there’s really no way around Safari on the iPhone, developers should perhaps just not use IndexedDB if the browser is Safari, given how buggy the implementation is. It pretty clear that Apple isn’t giving Safari/WebKit the focus it needs, but it’s also clear that developers just continue to push for more and more features in the browser. I’d much prefer that browsers started to cut back. While Google is excellent about updates, remember that critical bugs are found in Chrome constantly.
  • easrng 5y ago
    The problem is there's no alternative. LocalStorage is synchronous and has low limits, but works OK for things like preferences and auth tokens. If you are doing anything bigger like editing files then IndexedDB is your only option.
  • LAC-Tech 5y ago
    Maybe the way forward is to forge ahead without Safari, until pressure from customer forces them to implement this (and other web features). Already on chrome we can go to a URL, click the 'install' button, and have an app on our desktop/homepage. No app store, no massive download. I sincerely hope this is the future and not brilliant dead-end HN will be nostalgic about in 10 years.
  • cglong 5y ago
    Unfortunately, if I advertised my webapp as "Works Best in Chrome", people would claim I was "supporting the browser monoculture".
    • deleted 5y ago
      [deleted]
    • WhyNotHugo 5y ago
      That's rather binary thinking; just because you don't want to support Safari doesn't imply you should recommend Chrome.