Chrome Version: 60.0.3080.5
OS: Linux (also tested on Mac)

What steps will reproduce the problem?
(1) Open http://www.omnis.com/mozilla/test.html
(2) Enable "always allow pop-ups" on the pop-up notification in the URL bar
(3) Reload the page (notice the pop-up window open)
(4) Ctrl-Click on the link

What is the expected result?
In Chrome 59 only one new tab would be opened for the ctrl-click (the additional window.open call inside the page would just refer to the previously opened window).

What happens instead?
Starting sometime in Chrome 60 we see an additional "pop-up" tab opened on each ctrl-click (so two new tabs per ctrl-click instead of one).

It's not necessarily clear which behavior is right, but this new behavior has caused at least one web compat issue to be reported against Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1357845, so should at least consider the possible web-compat impact of this change (tentatively marking RBS-60 as a result).

I don't find ANY Blink>WindowDialog bugs fixed in the M60 timeframe which look like they could be responsible for this.  Can we please get a per-CL bisect to identify the CL that changed the behavior here?

 

Chrome Version: 60.0.3080.5
OS: Linux (also tested on Mac)

What steps will reproduce the problem?
(1) Open http://www.omnis.com/mozilla/test.html
(2) Enable "always allow pop-ups" on the pop-up notification in the URL bar
(3) Reload the page (notice the pop-up window open)
(4) Ctrl-Click on the link

What is the expected result?
In Chrome 59 only one new tab would be opened for the ctrl-click (the additional window.open call inside the page would just refer to the previously opened window).

What happens instead?
Starting sometime in Chrome 60 we see an additional "pop-up" tab opened on each ctrl-click (so two new tabs per ctrl-click instead of one).

It's not necessarily clear which behavior is right, but this new behavior has caused at least one web compat issue to be reported against Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1357845, so we should at least consider the possible web-compat impact of this change (tentatively marking RBS-60 as a result).

I don't find ANY Blink>WindowDialog bugs fixed in the M60 timeframe which look like they could be responsible for this.  Can we please get a per-CL bisect to identify the CL that changed the behavior here?