New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configuration.headless parameter is not taken into account while RemoteWebDriver is created. #660

Closed
saboteurserg opened this Issue Jan 3, 2018 · 0 comments

Comments

Projects
None yet
3 participants
@saboteurserg

saboteurserg commented Jan 3, 2018

The problem

Configuration.headless is not taken into account while RemoteWebDriver is created.

Details

Thus browser (tested with chrome) started normally, not headless. If create RemoteWebDriver manually and specify headless argument - everything working fine:

        ChromeOptions options = new ChromeOptions();
        options.addArguments("--headless");
        DesiredCapabilities capabilities = DesiredCapabilities.chrome();
        capabilities.setCapability(ChromeOptions.CAPABILITY, options);
        WebDriver driver = new RemoteWebDriver(new URL("http://localhost:4444/wd/hub"), capabilities);

Tell us about your environment

  • Selenide Version:4.9.1
  • Chrome: 63.0.3239.108 (Official Build) (64-bit)
  • Browser Driver Version:chromedriver-2.34.exe
  • Windows 7:

Code To Reproduce Issue [ Good To Have ]

Please remember that with sample code it's easier to reproduce the bug.

@BorisOsipov BorisOsipov self-assigned this Jan 3, 2018

BorisOsipov added a commit that referenced this issue Jan 3, 2018

Fix #660 - Remote driver factory should take into account headless op…
…tion

Signed-off-by: Boris Osipov <osipov.boris@gmail.com>

asolntsev added a commit that referenced this issue Jan 6, 2018

Merge pull request #661 from codeborne/#660_headless_remote_driver
Fix #660 - Remote driver factory should take into account headless option

@asolntsev asolntsev added this to the 4.10 milestone Jan 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment