зеркало из https://github.com/mozilla/gecko-dev.git
1fd7001f01
From browser.js's point of view there's no difference between restricted and guest profiles. Both use the parental controls API. So there are only two "simple" solutions here: * 1) Add a method to nsIParentalControlsService to determine whether the current profiles is a restricted or a guest profile (Something like isGuest()). But then every platform using this interface would require to at least implement a stub for this method. * 2) Add a new restriction that controls installing the theme. This patch implements option 2. While this restriction is not of much use besides deciding whether we need to install a specialized theme (DISALLOW_DEFAULT_THEME), it still offers the most flexibility. In a follow-up bug we could decide to make the restriction configurable by the device admin (requires localized strings). --HG-- extra : commitid : 1HcJmNLuz7b extra : rebase_source : d43407713b7d41a546213e75b7d5e4f03a8b3d78 |
||
|---|---|---|
| .. | ||
| components | ||
| content | ||
| crashreporter | ||
| devtools | ||
| forgetaboutsite | ||
| identity | ||
| library | ||
| locales | ||
| modules | ||
| mozapps | ||
| obsolete | ||
| profile | ||
| system | ||
| themes | ||
| webapps | ||
| xre | ||
| moz.build | ||
| toolkit.mozbuild | ||