Opened on 10/21/2014 at 01:49:53 PM
Closed on 04/20/2015 at 03:27:24 PM
Last modified on 04/21/2015 at 11:52:22 AM
#1488 closed change (fixed)
Add pre-configurable preference to suppress the first run page in Chrome
| Reported by: | sebastian | Assignee: | sebastian |
|---|---|---|---|
| Priority: | P3 | Milestone: | Adblock-Plus-1.9-for-Chrome-Opera-Safari |
| Module: | Platform | Keywords: | growth, large-scale-deployments |
| Cc: | mapx, simona, greiner | Blocked By: | #2040, #2171 |
| Blocking: | #542 | Platform: | Unknown |
| Ready: | yes | Confidential: | no |
| Tester: | Verified working: | no | |
| Review URL(s): | |||
Description (last modified by sebastian)
Background
In order to help administrators to deploy Adblock Plus in managed networks, we like to introduce pre-configurable preferences that can be configured via policies. For now that is only an option to prevent the first run page from showing up, which seems most important, since a lot of managed machines are reset on restart or login.
What to change
Implement the Managed Storage API. The key of the items retrieved, provides the name of a preference. The value should be used as default for that preference, overriding the hard-coded default value. However, values set by the user must override that default.
Add a managed storage schema declaring the boolean property suppress_first_run_page. Add that property as well to the Prefs object, and consider that preference when showing the first run page. If that preference is set to true the first run page must not show up.
Attachments (0)
Change History (18)
comment:1 Changed on 10/21/2014 at 02:04:10 PM by sebastian
- Blocking 278 added
comment:3 Changed on 10/21/2014 at 02:15:29 PM by mapx
- Cc mapx added
comment:4 Changed on 10/21/2014 at 02:17:30 PM by sebastian
- Owner sebastian deleted
comment:6 Changed on 10/30/2014 at 01:07:34 PM by simona
- Keywords growth added
comment:7 Changed on 11/21/2014 at 11:54:29 AM by simona
- Cc simona added
comment:8 Changed on 11/21/2014 at 04:21:11 PM by simona
- Keywords large-scale-deployments added
comment:9 Changed on 02/25/2015 at 01:40:52 PM by sebastian
- Blocked By 2040 added
comment:10 Changed on 03/19/2015 at 10:36:43 AM by sebastian
- Owner set to sebastian
comment:11 Changed on 03/19/2015 at 10:36:58 AM by sebastian
- Review URL(s) modified (diff)
- Status changed from new to reviewing
comment:12 Changed on 03/19/2015 at 11:09:53 AM by sebastian
- Blocked By 2171 added
comment:13 Changed on 03/20/2015 at 02:21:00 PM by sebastian
- Blocked By 1487 removed
- Description modified (diff)
- Summary changed from Enable pre-configurable properties in Chrome to Add pre-configurable preference to suppress the first run page in Chrome
comment:14 Changed on 03/20/2015 at 02:43:51 PM by sebastian
- Blocking 278 removed
comment:15 Changed on 03/20/2015 at 02:47:02 PM by greiner
- Cc greiner added
comment:16 Changed on 04/20/2015 at 03:27:24 PM by sebastian
- Milestone set to Adblock-Plus-for-Chrome-Opera-Safari-next
- Resolution set to fixed
- Status changed from reviewing to closed
comment:17 Changed on 04/20/2015 at 10:36:22 PM by Ross
This didn't work for me on a local (non-domain) Windows machine. Chrome appears to completely ignore registry keys for policies if they were not added via the Windows Group Policy Editor. Tested that out by attempting set an actual Chrome policy, (instead of extension policy), Chrome did indeed ignore it.
Attempted to test on VM's but could only set local policy. Going to try a template as suggested below / ask VM provider about changing settings.
Chrome 42.0.2311.90 / Windows 8.1 x64 / ABP: 1.8.12.1421
comment:18 Changed on 04/21/2015 at 10:29:04 AM by sebastian
According to the documentation provisioning policy via registry is only supported Windows instances that are joined to an Active Directory domain. I've updated the devbuild announcement receptively. Alternatively, one could write an ADM/ADMX template to configure that policy via GPO Editor.
https://hg.adblockplus.org/adblockpluschrome/rev/91d923ebcbd1