PopupsAllowedForUrls not adding urls to popup exception list
Reported by
viveknna...@gmail.com,
Sep 28 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Example URL: Steps to reproduce the problem: 1. I'm trying to "Allow popups on these sites" through group policy, admin templates. 2. I've put URLs in as exceptions and they don't populate in Chrome content settings on any domain computers. I listed domains as [*].website.com 4. I've set the policy as a Computer policy and User Policy. 5. Other policies do load such as home button, and homepage. 6. I've found that the corresponding registry key (HKLM\Software\Policies\Google\Chrome\PopupsAllowedForUrls) does have my correct URL values. Yet these do not show in Chrome popup exception list. Its empty What is the expected behavior? Popups are allowed for listed domains. What went wrong? Popups are still blocked for listed domains. Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? No Does this work in other browsers? N/A Chrome version: 61.0.3163.100 Channel: n/a OS Version: Windiows 7 Flash Version: Shockwave Flash 27.0 r0
,
Oct 4 2017
Unable to reproduce the issue on win 10 with chrome #61.0.3163.100 Steps followed: 1. Enabled policy allow popups for http://[*.]popuptest.com 2. Updated policy in win10 client machines Observations: 1. Policy is updated in chrome://policy, chrome://settings 2. On navigating to www.popuptest.com, popup's are displayed Attaching the screen-cast for reference viveknnambiar@ Could you please look into it and let us know any steps i have missed while reproducing the scenario. Thank You...
,
Oct 9 2017
+Julian Julian, would you know if policy registry keys read on Windows are processed in a case-sensitive way? If yes, this could explain the issue PopupsAllowedForUrls (policy name) vs. PopupsAllowedforUrls (from screenshot)
,
Oct 9 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 10 2017
Yes please try fixing the case of letters. Although the Windows registry is case insensitive it is case preserving and Chrome's code might be sensitive to that. You won't be able to rename the reg key just by changing the case (as from Win's perspective you have't changed it) but you can go through a dummy name and then to the properly cased name. If this doesn't help we can do further investigation.
,
Oct 16 2017
viveknnambiar@ Could you please respond to the comment #6
,
Nov 13 2017
,
May 22 2018
Closing issue as Wontfix due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested. Thanks..! |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by ligim...@chromium.org
, Sep 28 2017Components: Enterprise