what is the purpose for two separate indexedDB enabled features

RESOLVED INVALID

Status

()

RESOLVED INVALID
7 years ago
7 years ago

People

(Reporter: jhammink, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

7 years ago
dom.indexedDB.enabled = true
indexedDB.feature.enabled = true

This seems redundant.  Why are there two such settings in about:config?
OS: Android → All
Hardware: ARM → All
Target Milestone: mozilla11 → ---
indexedDB.feature.enabled controls whether the API is exposed on the Window object at all.  But this only applies to content windows; chrome windows always have the API.

dom.indexedDB.enabled controls what happens when you try to use the API.  It looks like this applies to chrome as well, as far as I can tell.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
Component: DOM: Core & HTML → DOM: IndexedDB
Version: Trunk → unspecified
You need to log in before you can comment on or make changes to this bug.