Unable to reproduce the issue on reported chrome version 63.0.3239.84 using windows 10 with steps mentioned below:

Steps to reproduce the issue:
1) Launched reported chrome version in incognito mode through terminal by disabling popup-blocking
2) Navigated to URL: http://www.popuptest.com
3) Able to see popup's on incognito window

@Reporter:
Please find the attached screencast for your reference and let us know if we missed anything from our end, please try to test this issue by creating new person with no extensions and apps in it and let us know if the issue still persists, provide the URL for which you are facing the issue which helps us in further triaging the issue.

Thanks!

Deleted: 796174.mp4 5.2 MB

	796174.mp4 5.2 MB View Download

Creating a local user on the machine and running the switches seems to work.  doing it on a domain account does not allow it to work. 

Looking into this further, it appears that it might be an issue with one or more chrome GPO's we have in place.  Thank you for your help with this.  I'll troubleshoot the GPO's we have turned on and let you know if the issue still persists. 

Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Here's a small update. 

1.) I've recreated the GPO
2.) Applied it to the test OU
3.) moved my user account into that OU
4.) had it apply the same GPO's as our production OU (minus the current chrome GPO)
5.) applied the newly created chrome GPO's (which are an exact copy of the original chrome GPO's)
6.) ran gpupdate /force on my VM
7.) logged out and back in
8.) running chrome.exe --incognito --disable-popup-blocking appeared in chrome://version
9.) popuptest.com is successful
10.) moved my user account back into the production OU with the original chrome GPO's
11.) Ran gpupdate /force
12.) Logged out and back in
13.) ran chrome.exe --incognito --disable-popup-blocking and it appears to be passing the switches through the command line.  

I don't understand what would prevent it from passing the switches when a simple "refresh" of the GPO's seems to resolve it.  I'll do more testing on this in the next day or two.  

Unable to reproduce this issue on Windows 7, Windows 10 with chrome #63.0.3239.84

Steps Followed :
1. Enabled popup policy on both server and client
2. Launched chrome incognito window
3. Navigated to www.popuptest.com

Observed :
1. In in-cognito window, popups are not blocked.

Attaching the screen-cast for reference.

bellopheron@ Could you please look into it and let us know any steps i have missed while reproducing the scenario.

pastarmovj@ Could you please look into this issue and update accordingly.


Thank You...

 

Deleted: 796174.mp4 1.7 MB

	796174.mp4 1.7 MB View Download

the steps look like you covered everything.  The biggest different i've found is your policy screen has less policies applied to it than ours:

Deleted: chrome policy.png 55.9 KB

	chrome policy.png 55.9 KB View Download

Here's the SS of the chrome://version screen

Deleted: Chrome version.png 84.7 KB

	Chrome version.png 84.7 KB View Download

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

I will recap my understanding of this issue so far. Please correct it if it is wrong:

1. Using GPO to disable the popup blocker works in incognito.
2. Using the command line flag --disable-popup-blocking doesn't.
3. The statement in nr. 2 is the problem that is reported.

Testing 2 manually on the most recent canary seems to work as expected btw. Both when running chrome with the --incognito flag or when manually opening upan incognito window afterwards.

1.)  We haven't tried to use the GPO to disable the popupblocker in either incognito or normal usage.  We would prefer that it stays enabled for normal use except when called for with the switches.

2.)  Correct.  In the screenshot i submitted back on 12/21, i ran the command   chrome.exe --incognito --disable-popup-blocking.  What seems to fix the issue is "refreshing" the GPO to allow the command line flag to get passed through to the exe.  

If the policy is not set and you need to run gpupdate this is rather weird as it has no influence normally on.

@kkaluri: Can you please try to recreate the same set of policies as in the screenshot and retry your test. If we have some interference there this is a bug and should be fixed.

Removing permissions model label as this appears to be a enterprise policy issue.

As per comment #17 again retested this scenario on chrome #63.0.3239.84 as per policies mentioned in the comment #12.

Still doesn't able to repro the scenario. Observed that in in-cognito mode, pop-ups are not blocked.

Attaching the screen-cast for reference.

Note: Since TE doesn't able to reproduce the scenario, removing needs-bisect label for now.

Deleted: 796174.mp4 1.3 MB

	796174.mp4 1.3 MB View Download

As per comments#11 and #20 issue is not reproducible from TE end in Enterprise environment. Hence adding TE-NeedsTriageHelp label for further investigation from dev team.

Thanks!

Not reproducing