Private Browsing on Firefox disables IndexedDB

[Rektroth]

I have tested using LiveSplitOne on my chromium browser, and it worked fine on there.

On Firefox, LiveSplitOne gets stuck on the loading screen. A quick look at the console reveals the following message:

Uncaught (in promise) DOMException: A mutation operation was attempted on a database that did not allow mutations. bundle.js:1:62182
  c           https://one.livesplit.org/bundle.js:1
  (Async: promise callback)
  b           https://one.livesplit.org/bundle.js:1
  a           https://one.livesplit.org/bundle.js:1
  (Async: promise callback)
  b           https://one.livesplit.org/bundle.js:1
  a           https://one.livesplit.org/bundle.js:1
  (Async: promise callback)
  b           https://one.livesplit.org/bundle.js:1
  a           https://one.livesplit.org/bundle.js:1
  (Async: promise callback)
  b           https://one.livesplit.org/bundle.js:1
  a           https://one.livesplit.org/bundle.js:1
  (Async: promise callback)
  b           https://one.livesplit.org/bundle.js:1
  l           https://one.livesplit.org/bundle.js:1
  l           https://one.livesplit.org/bundle.js:1
  <anonymous> https://one.livesplit.org/bundle.js:1
  <anonymous> https://one.livesplit.org/bundle.js:1
  a           https://one.livesplit.org/bundle.js:1
  <anonymous> https://one.livesplit.org/bundle.js:1
  a           https://one.livesplit.org/bundle.js:1
  <anonymous> https://one.livesplit.org/bundle.js:1
  <anonymous> https://one.livesplit.org/bundle.js:1

[CryZe]

It seems like IndexedDB is not usable at all when you are using Firefox's private browsing.

[CryZe]

Apparently they consider this a bug in Firefox and are currently intending to fix this: https://bugzilla.mozilla.org/show_bug.cgi?id=1639542

[qwertychouskie]

Looks like this should be fixed in the upcoming Firefox 115

[CryZe]

Yeah this seems to be fixed.