Open Bug 1194170 Opened 9 years ago Updated 2 years ago

Something in profile causes indexedDB InvalidStateError "A mutation operation was attempted on a database that did not allow mutations."

Categories

(Core :: Storage: IndexedDB, defect, P3)

Unspecified
Windows 7
defect

Tracking

()

UNCONFIRMED

People

(Reporter: serejkasimanovich, Unassigned)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:40.0) Gecko/20100101 Firefox/40.0
Build ID: 20150807085045

Steps to reproduce:

1. Open https://mdn.mozillademos.org/en-US/docs/IndexedDB/Using_IndexedDB$samples/Full_IndexedDB_example
2. See console


Actual results:

During attempt to open indexedDB triggered error callback with InvalidStateError. See screenshots.


Expected results:

indexedDB should open and call success callback.
OS: Unspecified → Windows 7
Component: Untriaged → General
Product: Firefox → Mozilla Developer Network
Version: 40 Branch → unspecified
This works for me using a clean profile (OS X Nightly), but I do get InvalidStateError if I try to open the page in the Private browsing mode.

Can you reproduce in a clean profile? Do you have history/privacy settings that might affect this perhaps?

kohei, do you have reasons to believe this is a problem with the MDN sample and not with the client settings?
Flags: needinfo?(serejkasimanovich)
Summary: indexedDB InvalidStateError → indexedDB InvalidStateError "A mutation operation was attempted on a database that did not allow mutations." using the MDN sample
(In reply to Nickolay_Ponomarev from comment #2)
> This works for me using a clean profile (OS X Nightly), but I do get
> InvalidStateError if I try to open the page in the Private browsing mode.
> 
> Can you reproduce in a clean profile? Do you have history/privacy settings
> that might affect this perhaps?
> 
> kohei, do you have reasons to believe this is a problem with the MDN sample
> and not with the client settings?

Yes, this problem reproduced since 38 on this current PC. Re-install, and clearing profile data doesn't solved issue. It doesn't belong to this sample, no one demo which use indexedDB works, receive same error.
Flags: needinfo?(serejkasimanovich)
(In reply to Nickolay_Ponomarev from comment #2)
> This works for me using a clean profile (OS X Nightly), but I do get
> InvalidStateError if I try to open the page in the Private browsing mode.
> 
> Can you reproduce in a clean profile? Do you have history/privacy settings
> that might affect this perhaps?
> 
> kohei, do you have reasons to believe this is a problem with the MDN sample
> and not with the client settings?

When deleted fully Profile directory error disappear, but I'm interested in common solution for users, who may not know about how delete this folder and so on, cause in some cases problem can be reproduced.
Do you still have the broken profile data available?
Component: General → DOM: IndexedDB
Product: Mozilla Developer Network → Core
Summary: indexedDB InvalidStateError "A mutation operation was attempted on a database that did not allow mutations." using the MDN sample → Something in profile causes indexedDB InvalidStateError "A mutation operation was attempted on a database that did not allow mutations."
(In reply to Nickolay_Ponomarev from comment #5)
> Do you still have the broken profile data available?

Unfortunatelly no.
Most likely this hit bug #1192643 (may have set to block offline storage for all sites in the permissions manager which disables IndexedDB).
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: