Closed Bug 1123423 Opened 9 years ago Closed 6 years ago

Remove the dom.indexedDB.enabled pref

Categories

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

Product:
Core
Component:
Storage: IndexedDB
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1488583

People

(Reporter: Ms2ger, Unassigned)

Details

      No description provided.
dev-doc-needed so we check if we still have occurence of it in the MDN when it lands.
Keywords: dev-doc-needed
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Not the same thing.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
It is either a duplicate of 1079355 or WONTFIX. Please see the discussion we had in the other bug.
Until IndexedDB is handled in the same way as cookies with respect to accepting/clearing and third-party behavior, this pref should exist.
Priority: -- → P5
Duping to bug 1488583 which is the same idea (eliminate the pref) but with some additional explanation/context to eliminate confusion.

(In reply to oyenamit from comment #5)
> Until IndexedDB is handled in the same way as cookies with respect to
> accepting/clearing and third-party behavior, this pref should exist.

Happily, IndexedDB responds to the same storage decision-making process for accepting cookies and the clearing mechanisms have been updated to also clear IndexedDB.  (In the past, it was true that there were several ways to clear data and these could potentially fail to include the relevant IndexedDB data.)
Status: REOPENED → RESOLVED
Closed: 9 years ago → 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.