Closed
Bug 1184064
Opened 9 years ago
Closed 9 years ago
Restricted Profiles: Change behavior of isUserRestricted()
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: sebastian, Unassigned, Mentored)
References
Details
Follow-up from bug 1181660.
Currently we assume the user is using a restricted profile whenever we find a restriction in the system's list of restrictions (getUserRestrictions()). As soon as bug 1180653 lands we will store our restrictions in the user manager too. After that we can check getApplicationRestrictions() to see if our app is restricted and then assume the profile is restricted.
Reporter | ||
Comment 1•9 years ago
|
||
Additionally we could think of making isUserRestricted() not accessible from other class. Instead callers should ask for a specific restriction instead of implementing their own logic.
Updated•9 years ago
|
Reporter | ||
Comment 2•9 years ago
|
||
We now have (and will have) code that should not run for restricted profiles (no matter what restrictions are in place).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•