Hey everyone (again..), In Firefox 42 we are shipping support for restricted profiles (bug 1125984 [1]) to create a more kid-friendly browsing experience.
In this first iteration we mostly focused on hiding complex or kid-unfriendly features. Of course this has a high risk of breaking in the future: It's easy to forget this when refactoring or adding a new feature. And in addition to that we might not have many testers using restricted profiles (Testers welcome!). As an example: This is the patch that hides "Private browsing" everywhere if the device admin decides to disable the feature: https://bug1125290.bmoattachments.org/attachment.cgi?id=8641005 First I didn't even know about all the ways to enter a private browsing session before writing this patch and then it's imaginable that we might add new ways (tab queues!) and forget to add these checks. I don't know of any good code pattern to prevent this (does anyone?). For example for private browsing we are thinking of short-circuiting the tab creation code (bug 1189344 [2]) but of course this does not magically hide all buttons in the UI. So yeah, the purpose of this mail is to just make everyone aware of restricted profiles to hopefully prevent some regressions. Best, Sebastian [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1125984 [2]: https://bugzilla.mozilla.org/show_bug.cgi?id=1189344
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
