Sebastian Kaspari 980ffb55da Bug 1199596 - Only install "Parental Controls Theme" for restricted profiles and not guest profiles. r=ally ... 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).		2015-08-31 18:09:42 +02:00
..
moz.build	Bug 1198334 (part 1) - Replace the opt-in FAIL_ON_WARNINGS with the opt-out ALLOW_COMPILER_WARNINGS. r=glandium.	2015-08-27 20:44:53 -07:00
nsIParentalControlsService.idl	Bug 1199596 - Only install "Parental Controls Theme" for restricted profiles and not guest profiles. r=ally	2015-08-31 18:09:42 +02:00
nsParentalControlsService.h
nsParentalControlsServiceAndroid.cpp	Bug 1192077 - Convert AndroidBridge JNIEnv calls; r=esawin	2015-08-13 00:53:39 -04:00
nsParentalControlsServiceCocoa.mm
nsParentalControlsServiceDefault.cpp
nsParentalControlsServiceWin.cpp	Bug 1134923 - Remove NS_Alloc/NS_Realloc/NS_Free. r=nfroyd	2015-05-01 09:40:30 +09:00