Status: Unconfirmed Owner: all-bugs-t...@chromium.org Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 7147 by nigel.kersten: Mac Chrome should be able to be centrally managed with MCX preferences/manifest http://code.google.com/p/chromium/issues/detail?id=7147 Chrome Version : N/A URLs (if applicable) : N/A Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 3: N/A Firefox 3: N/A IE 7: N/A What steps will reproduce the problem? 1. N/A 2. N/A 3. N/A What is the expected result? N/A What happens instead? N/A Please provide any additional information below. Attach a screenshot if possible. This is a feature request for the unreleased Mac version of Chrome. MCX is the equivalent of Group Policy under Windows. It would help enterprise/education deployment of a future Mac version of Chrome if preferences could be centrally managed using MCX controls. Ideally all settings could be manageable via MCX controls, but the crucial ones that are often used in enterprise/education deployments are: * browser homepage * proxy settings * whether self-update is enabled * whether javascript is enabled * whether java is enabled * whether passwords are remembered * If preferences are to be managed, the appropriate GUI controls for the end user should be disabled as per the following document from Apple: https://developer.apple.com/iphone/library/documentation/CoreFoundation/Conceptual/CFPreferences/Concepts/BestPractices.html#//apple_ref/doc/uid/TP30001219-118191 It would be even better if Chrome provided a preference manifest to make this sort of management easier with human readable names and descriptions for preference settings. See the Apple documentation for more details: http://developer.apple.com/DOCUMENTATION/MacOSXServer/Conceptual/Preference_Manifest_Files/Preface/chapter_1_section_1.html#//apple_ref/doc/uid/TP40001805-CH204-DontLinkElementID_4 As far as the various preference domains go, I would like to see Chrome be able to be managed at the user, group and computer level. For a complete first class MCX experience, these preferences should also be able to be managed in either the "Once", "Often" or "Always" MCX Domains. "Often" is much less crucial than "Always" or "Once" for most deployments. Once - Provides a default setting that users are allowed to override. Often - Preferences are set at irregular intervals. App launch, login etc. The user can override the setting, but it is restored at launch/login. Always - Overrides any user preferences and disables GUI controls to set such preference. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
