Closed Bug 783511 Opened 12 years ago Closed 12 years ago

Hook up Device Storage/ MediaStorage API to permissions manager

Categories

(Core :: General, defect)

Product:
Core
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Project Flags:
blocking-basecamp +

People

(Reporter: rforbes, Assigned: dougt)

References

Details

(Whiteboard: [WebAPI:P0]) 

I don't see a bug for this, if one has been made feel free to dup.
blocking-basecamp: --- → ?
Assignee: nobody → doug.turner
blocking-basecamp: ? → +
this already happens via the content permission prompt.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
We may have a content prompt, but that's not the same UX as our permission dialogs that go through the permission manager.  That needs to be a consistent experience, so reopening until we verify that we are talking about the same thing.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Whiteboard: [WebAPI:P0]
all apis go throught he content permission prompting code (indexed db does something else cause they have quotas).  This API allows the front end application to display any type of UI they want (or not).  In FF Desktop, this API has a door hanger UI.  In B2G, there is some ugly (now) permission dialog.

Device Storage already uses this permission manager.

So, I am not sure what action there is to take on this bug, and believe it should be WFM
not blocking as near as I can tell.
blocking-basecamp: + → ?
OK, makes sense to me.  Closing for now.
Status: REOPENED → RESOLVED
Closed: 12 years ago → 12 years ago
Resolution: --- → WORKSFORME
We wouldn't want this to regress.
blocking-basecamp: ? → +
You need to log in before you can comment on or make changes to this bug.