Decide how devicestorage permissions should be reflected in the page-exposed API

RESOLVED INCOMPLETE

Status

()

Core
DOM: Device Interfaces
RESOLVED INCOMPLETE
5 years ago
6 months ago

People

(Reporter: bz, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [DeviceStorageInvestigate])

Right now, navigator.getDeviceStorage does not check any permissions.  Trying to _use_ the resulting storage object can, though.

This bug is for figuring out what the setup here should look like.
So, if it winds up being desirable for a permissions check to be done, this could check that the caller has any perission.

Right now, there are 3 permissions for each storage type (the argument passed into getDeviceStorage)

device-storage:type-read
device-storage:type-write
device-storage:type-create

Presumably we could check if the caller has any of the 3 and only return a non-null result if that is in fact the case.
Note that there are several things we can do here with permissions checks:

1)  Change what getDeviceStorage returns.  This can make use of the type argument for getDeviceStorage.

2)  Change whether navigator.getDeviceStorage exists at all.  This obviously can't depend on the storage type.
Whiteboard: [DeviceStorageInvestigate]
FxOS/Gonk has been removed from the codebase. Mass-invalidating FxOS related Device Interface bugs to clean up the component. 

If I incorrectly invalidated something, please let me know.
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → INVALID
Bulk correction of resolution of B2G bugs to INCOMPLETE.
Resolution: INVALID → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.