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

Status: RESOLVED INCOMPLETE

(Core :: DOM: Device Interfaces, defect)

Description

[Boris Zbarsky [:bzbarsky]]

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.

Comment 1

[Dave Hylands [:dhylands]]

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.

Comment 2

[Boris Zbarsky [:bzbarsky]]

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.

Comment 3

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

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.

Comment 4

[Firefox Bug Husbandry Bot]

Bulk correction of resolution of B2G bugs to INCOMPLETE.