Closed
Bug 818566
Opened 12 years ago
Closed 12 years ago
Permissions Installer - states that a privileged app can access the camera API via PROMPT_ACTION, but permissions matrix says it should be DENY_ACTION
Categories
(Firefox OS Graveyard :: General, defect, P1)
Tracking
(blocking-basecamp:+, firefox19 fixed, firefox20 fixed, b2g18 fixed)
RESOLVED
FIXED
blocking-basecamp | + |
People
(Reporter: jsmith, Assigned: gwagner)
References
Details
(Whiteboard: [qa-])
Attachments
(1 file)
1014 bytes,
patch
|
sicking
:
review+
|
Details | Diff | Splinter Review |
The permissions installer for camera states the following: 48 camera: { 49 app: DENY_ACTION, 50 privileged: PROMPT_ACTION, 51 certified: ALLOW_ACTION 52 }, http://mxr.mozilla.org/mozilla-central/source/dom/apps/src/PermissionsInstaller.jsm However, the permissions matrix states that privileged should be DENY_ACTION. Which is not right? The doc or the code?
Reporter | ||
Comment 1•12 years ago
|
||
Noming in case the code is wrong. If the doc is wrong, then minus and state to update the doc.
Blocks: finalize-permissions
blocking-basecamp: --- → ?
Reporter | ||
Comment 2•12 years ago
|
||
Permissions matrix: https://docs.google.com/spreadsheet/ccc?key=0Akyz_Bqjgf5pdENVekxYRjBTX0dCXzItMnRyUU1RQ0E#gid=0
Comment 3•12 years ago
|
||
The purpose of Privileged Apps is to allow developers everywhere to create HTML-based apps that can do things previously reserved for "real" (native) apps. Considering the popularity of apps like Instagram, we must allow Privileged Apps to access the camera. Note that I'm not talking about switching away to the built-in Camera app using an Intent or Activity, but rather I'm talking about getting continuous access to the live camera preview so I can apply creative filters.
Updated•12 years ago
|
Assignee: nobody → bjacob
blocking-basecamp: ? → +
Updated•12 years ago
|
Assignee: bjacob → anygregor
Comment 4•12 years ago
|
||
Can we get a priority and target milestone for this>
Comment 5•12 years ago
|
||
(In reply to Bill Walker [:bwalker] [@wfwalker] from comment #3) > The purpose of Privileged Apps is to allow developers everywhere to create > HTML-based apps that can do things previously reserved for "real" (native) > apps. > > Considering the popularity of apps like Instagram, we must allow Privileged > Apps to access the camera. Note that I'm not talking about switching away to > the built-in Camera app using an Intent or Activity, but rather I'm talking > about getting continuous access to the live camera preview so I can apply > creative filters. No disagreement about the goal here, however the implementation reality is that the camera API as implemented for basecamp is incompatible with process sandboxing, meaning any app that wants direct access to camera will need to break out of the sandbox. Its something we want to fix, but realistically not for basecamp.
Updated•12 years ago
|
Priority: -- → P1
Assignee | ||
Comment 6•12 years ago
|
||
Attachment #690257 -
Flags: review?(jonas)
Attachment #690257 -
Flags: review?(jonas) → review+
Assignee | ||
Comment 7•12 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/0770315e3538
Comment 8•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/0770315e3538
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•12 years ago
|
Whiteboard: [qa-]
Comment 9•12 years ago
|
||
https://hg.mozilla.org/releases/mozilla-aurora/rev/97b22dbac0d1 https://hg.mozilla.org/releases/mozilla-b2g18/rev/35b8db6c3dcc
status-firefox19:
--- → fixed
status-firefox20:
--- → fixed
Whiteboard: [qa-] → [qa-][status-b2g18:fixed]
Updated•12 years ago
|
status-b2g18:
--- → fixed
Whiteboard: [qa-][status-b2g18:fixed] → [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•