It works on Chrome 63.0.3239.18 (Official Build) beta (64-bit)

Forgive me if I'm mistaken, but it seems like this API is not about opening "popups" in the same sense as the popup blocker. These popups seem like lightbox-style widgets on the original page.

FWIW I can reproduce this on M62 stable Mac, but not on M64 Mac canary.

I bisected the fix to:
https://chromium.googlesource.com/chromium/src/+log/2fa59ed505a54ea19c425854c70eeae0590145ff..115ac3528d0a279b55f5ec5ae82a872db9da3911

I haven't bisected the regression though. Perhaps someone in the fix range can comment.

Maybe https://chromium.googlesource.com/chromium/src/+/9f0c480da9cb188c82e16e6c6751875a60a114cf? Not sure how to best contact Rune since it seems like their opera acct is not monitored. cc naina instead.

The CL in the bisect range was reverted in 64, so that would explain why canary doesn't have this. 

Marking the bug as Fixed in that case?

Any chance it might need a merge to M63/62?

The CL in the bisect range *is* the fix, since I bisected the fix range. I looks like that landed in M63, so it would only need merge to M62 (if it is necessary).

hmm strange - I reverted the CL in 64 so you should see the issue in both 62 and 64 but not in 63.

Hm, are we sure that CL is the right fix in the fix range? Maybe there's another culprit.

That could be the case. FWIW. I cant seem to repro the issue on 61, 63 or 64. Attaching screenshots

Deleted: m61.png 44.0 KB

	m61.png 44.0 KB View Download

Deleted: m63.png 34.5 KB

	m63.png 34.5 KB View Download

Deleted: m64.png 34.7 KB

	m64.png 34.7 KB View Download

Deleted: Screen Shot 2017-10-27 at 10.28.38 AM.png 17.1 KB

	Screen Shot 2017-10-27 at 10.28.38 AM.png 17.1 KB View Download

Able to reproduce the issue on Windows 10, Mac 10.12.6 and Ubuntu 14.04 using reported version #62.0.3202.75 but the same is not reproducible in the latest canary #64.0.3253.0 and latest beta #63.0.3239.18.

Reverse Bisect Information:
=====================
Good build: 63.0.3226.0  Revision(504841)
Bad Build : 63.0.3225.0  Revision(504540)

Change Log URL: 
https://chromium.googlesource.com/chromium/src/+log/a9ba55c8571ab0d2624c83d413ccc7215a185f51..9f0c480da9cb188c82e16e6c6751875a60a114cf

From the above change log possible CL that fixed this issue:
Change-Id: Iee509e43e5fcc29d04944655d3d966ea61cc2adf
Reviewed-on: https://chromium-review.googlesource.com/684186 

nainar@ - Could you please check and merge the fix to M63 if it is a valid candidate.
Note: Assigning to the reviewer of the issue as the author's id i.e rune@opera.com doesn't seems to be valid anymore.
Adding label ReleaseBlock-Stable as it seems to be a recent regression.

Thanks...!!

Correction:
As no issue is observed in latest beta #63.0.3239.18. Hence, requesting the merge to M-62.
Thanks...!!

What is the exact user impact for this bug? Is it blocking any functionality and/or is there a workaround?

Can you provide me with a video recording of this issue's repro so that I can better understand priority? Thank you!

nainar@, here is the expected behavior. As per c#15, this doesn't repro on M63 & M64 because of this CL: https://chromium-review.googlesource.com/684186.

Seems like the root cause is same for both crbug/778631 & current issue (crbug/779051) ?

Thank you!

Deleted: 779051.mp4 1.0 MB

	779051.mp4 1.0 MB View Download

I am hesitant to merge this to 62, since I didn't write the original code. Would feel more comfortable keeping this in 63 only and letting the change move to stable with 63. 

[Bulk Edit]
URGENT - PTAL.
M63 Stable promotion is coming soon and your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the release branch ASAP. Thank you.