Issue metadata
Sign in to add a comment
|
Extensions installed via group policy do not display a 'background page' link
Reported by
ithai.me...@gmail.com,
Sep 6
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36 Steps to reproduce the problem: 1. Add hangouts extension from the chrome store, navigate to chrome://extensions --> you'll have access to the background page 2. Add hangouts by group policy (nckgahadagoaajjgafhacjanaoiihapd;https://clients2.google.com/service/update2/crx) --> no access to the background page 3. What is the expected behavior? Have access to the background page of extensions install by group policy What went wrong? No access to the background page of extensions install by group policy Did this work before? Yes 68.0.3440.106 Chrome version: 69.0.3497.81 Channel: stable OS Version: 10.0 Flash Version: Critical issue for developers of unlisted extensions
,
Sep 7
,
Sep 7
Unable to reproduce this issue on Windows 10 with chrome #69.0.3497.81 as per steps mentioned in comment #0 On Enabling the developer mode, able to access the background page for hangout extension. Attaching the screen-cast for reference. ithai.meier@ Could you please look into it and let us know your observations.
,
Sep 24
,
Sep 28
I have the same issue running Chrome 69.0.3497.100 on Windows 10. If the extension is installed via gpo the background page link does not appear. It it is installed directly from the store the background page is accessible.
,
Oct 2
@kkaluri, I'm a colleague of the OP. Are you sure you installed the extension via group policy? (the screen capture doesn't show the installation mechanism). To be clear: to reproduce, install a fresh chrome 69 and run the attached reg file. Its contents are: ------------------------ Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionInstallForcelist] "1"="nckgahadagoaajjgafhacjanaoiihapd;https://clients2.google.com/service/update2/crx" ------------------------ For us it is 100% reproducible, on multiple machines.
,
Oct 3
,
Oct 11
Any success in reproducing? This is a serious issue for us.
,
Oct 11
Ofek, is that you? Gmail?
,
Oct 23
This is a blocker for us. It is impeding our ability to gather logs from customer devices for debugging. Is there a workaround? Steps to repro: 1. Login to https://admin.google.com 2. Navigate to Device management > Chrome > User Settings > Force-installed Apps and Extensions > Manage force-installed apps 3. Add extension to be force-installed on ChromeOS 4. Go to chrome://extensions on device once extension is pushed. Background page will not be visible. Installing the same extension directly on ChromeOS shows the Background Page though.
,
Nov 6
Hello dear Chromium devs, any updates on this issue?
,
Jan 13
Based upon the code comments found here: https://cs.chromium.org/chromium/src/chrome/browser/policy/developer_tools_policy_handler.h?type=cs&g=0&l=32 I believe this might be working as intended. In order to circumvent this and allow the inspection of background pages with a GPS, you may want to set the DeveloperToolsAvailability GPO which can be found here: https://www.chromium.org/administrators/policy-list-3#DeveloperToolsAvailability
,
Jan 13
Just tested the developer tools availability setting and by setting the DWORD to 1, we were able to see the developer tools when we turned extension developer mode on. Hope this helps.
,
Jan 13
I confirm too - the registry key works. Thanks!
,
Jan 13
Great! Glad we were able to get you moving again. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by viswa.karala@chromium.org
, Sep 6