Closed Bug 818596 Opened 13 years ago Closed 13 years ago

Permissions Installer - states that a privileged app can't access wifi-manage, but permissions matrix says it should via PROMPT_ACTION

Categories

(Firefox OS Graveyard :: General, defect, P1)

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:-)

RESOLVED FIXED
blocking-basecamp -

People

(Reporter: jsmith, Unassigned)

References

Details

The permissions installer states the following: 176 "wifi-manage": { 177 app: DENY_ACTION, 178 privileged: DENY_ACTION, 179 certified: ALLOW_ACTION 180 }, However, the permission matrix says that a privileged app can access wifi-manage via PROMPT_ACTION. Is the doc wrong or the is the code wrong?
blocking-basecamp: --- → ?
Spoke with Gregor in IRC - all of them going his way to resolve the contention.
Assignee: nobody → anygregor
blocking-basecamp: ? → +
Priority: -- → P1
We won't have time to do this for v1. Fixing this will require some small changes to the API to make it asynchronous (so that we can wait with taking action until the user has acted on the prompt) as well as UI changes to implement the new prompt. It's too late to make that happen in v1. If this is a strict product requirement, please do renominate this bug.
Assignee: anygregor → nobody
blocking-basecamp: + → -
We'll probably want to update the doc in this case for v1.
Updated spreadsheet to reflect this decision.
Resolving since spreadsheet is now correct and no code change is needed. Reopen if you disagree.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.