Closed
Bug 707626
Opened 13 years ago
Closed 13 years ago
Hook up screen.mozEnabled, screen.mozBrightness to permission API
Categories
(Core :: General, defect, P1)
Tracking
()
RESOLVED
FIXED
| blocking-basecamp | + |
People
(Reporter: justin.lebar+bug, Unassigned)
References
Details
Once we have the permission manager from bug 707625, we need to hook up screen.mozEnabled and screen.mozBrightness to it.
|
||
Comment 1•13 years ago
|
||
Until we have a new permission manager, can we use the 'old' one to hook up those properties to the content?
We're already using it for indexedDB, offline-storage, webapps-manage, etc...
I remember it being said to steer clear of the old permissions manager.
Any advice?
|
Reporter | |
Comment 3•13 years ago
|
||
FWIW, right now we're doing pref-based "permission management" in WebSMS and the browser API stuff I've been doing.
Depends on: 729430
|
||
Updated•13 years ago
|
blocking-basecamp: --- → +
https://docs.google.com/spreadsheet/ccc?key=0Akyz_Bqjgf5pdENVekxYRjBTX0dCXzItMnRyUU1RQ0E#gid=0 says this Permission Name is "power".
I'm apply the process-level capability check in bug 776835.
No longer blocks: 776652
|
||
Updated•13 years ago
|
Priority: -- → P1
|
||
Comment 5•13 years ago
|
||
Fixed in bug 781353
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.
Description
•