Closed Bug 707626 Opened 13 years ago Closed 12 years ago

Hook up screen.mozEnabled, screen.mozBrightness to permission API

Categories

(Core :: General, defect, P1)

Product:
Core
Component:
General
Platform:
All
Gonk (Firefox OS)
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Project Flags:
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.
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?
FWIW, right now we're doing pref-based "permission management" in WebSMS and the browser API stuff I've been doing.
No longer depends on: 707625
Depends on: 707625
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
Priority: -- → P1
Depends on: 781353
Fixed in bug 781353
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.