Chromedriver triggered chrome instance ignores popup blocking settings
Reported by
awojtc...@xtm-intl.com,
Apr 15 2018
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36 Steps to reproduce the problem: 1. Create WebDriver node that is able to serve Chrome browser based driver. 2. via RemoteWebDriver poll for a chrome browser with argument "disable-popup-blocking" 3. Trigger opening new single-tab window What is the expected behavior? Page that is meant to be loaded in new single-tab window opens in the tab it was triggered from. What went wrong? New single-tab windows is opened. Did this work before? N/A Chrome version: 65.0.3325.181 Channel: stable OS Version: 10.0 Flash Version: Having the chromedriver triggered instance opened I checked page content settings and pop-ups : blocked was set correctly. Switching back on and off did not help. Another crazy thing is... in chrome instance that is not chromedriver triggered it works fine - with pop-ups blocked setting the same page does not open new window. Newest as for today (2.37) chromedriver version.
,
Apr 16 2018
The issue seems to be out of TE-scope as it is related to chrome web driver. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team. Thanks...!!
,
Apr 16 2018
The behavior is by design. By default, ChromeDriver passes --disable-popup-blocking switch to Chrome, so that opening new tabs is always allowed, regardless of page content settings.
,
Apr 19 2018
Is this switch is not supposed to block opening new tabs, which switch will do the job? I'm looking for an option like "firefox's dom.popup_maximum (0 means no other windows shall be opened). |
|||
►
Sign in to add a comment |
|||
Comment 1 by susan.boorgula@chromium.org
, Apr 15 2018