Skip to content
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

Element is not clickable in Chrome Headless #4685

Closed
mh884 opened this issue Sep 12, 2017 · 23 comments
Closed

Element is not clickable in Chrome Headless #4685

mh884 opened this issue Sep 12, 2017 · 23 comments

Comments

@mh884
Copy link

@mh884 mh884 commented Sep 12, 2017

I have a problem with clicking on the element from headless Chrome this call worked some time Without Headless Chrome and does not work at all with Headless

Call
driver.FindElement(By.Id("createBtn"))

Element
{Element (id = 0.18579689918655928-11)}
Coordinates: {OpenQA.Selenium.Remote.RemoteCoordinates}
Displayed: true
Enabled: true
Id: "0.18579689918655928-11"
Location: {X = 808 Y = 343}
LocationOnScreenOnceScrolledIntoView: {X = 808 Y = 343}
Selected: false
Size: {Width = 121 Height = 40}
TagName: "a"
Text: "Create"
WrappedDriver: {OpenQA.Selenium.Chrome.ChromeDriver}

Error:
Message: System.InvalidOperationException : unknown error: Element is not clickable at point (868, 363)
(Session info: headless chrome=61.0.3163.79)
(Driver info: chromedriver=2.31.488763

@robinbobin25

This comment has been minimized.

Copy link

@robinbobin25 robinbobin25 commented Sep 12, 2017

+1 Have similar issue with chrome Version 61.0.3163.79 (Official Build) (64-bit) and Selenium version: '3.5.3'

org.openqa.selenium.WebDriverException: unknown error: Element is not clickable at point (1268, 1175)
  (Session info: chrome=61.0.3163.79)
  (Driver info: chromedriver=2.30.477700 (0057494ad8732195794a7b32078424f92a5fce41),platform=Windows NT 10.0.15063 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 0 milliseconds

With the previous Chrome version is OK

@Shkvarka

This comment has been minimized.

Copy link

@Shkvarka Shkvarka commented Sep 12, 2017

Same issue here, but in UI mode, tried Selenium 3.4.0 and 3.5.3, Chrome Version 61.0.3163.79 (Official Build) (64-bit)

@barancev

This comment has been minimized.

Copy link
Member

@barancev barancev commented Sep 12, 2017

Please retest with chromedriver 2.32

@Shkvarka

This comment has been minimized.

Copy link

@Shkvarka Shkvarka commented Sep 12, 2017

Alexey, yes, it fix the issue. Thank you

@mh884 mh884 closed this Sep 12, 2017
MatthewWilkes added a commit to Dallinger/Griduniverse that referenced this issue Sep 29, 2017
MatthewWilkes added a commit to Dallinger/Griduniverse that referenced this issue Sep 29, 2017
@HartBlanc

This comment has been minimized.

Copy link

@HartBlanc HartBlanc commented Jan 5, 2018

I'm still having this issue in 2.34

@sandboxzor

This comment has been minimized.

Copy link

@sandboxzor sandboxzor commented Jan 12, 2018

Also with 2.35

@wilsonfcit

This comment has been minimized.

Copy link

@wilsonfcit wilsonfcit commented Jan 17, 2018

Also with 2.35!

@WaldenLian

This comment has been minimized.

Copy link

@WaldenLian WaldenLian commented Feb 6, 2018

I also have this issue with chromedriver 2.35.

@SamCosta1

This comment has been minimized.

Copy link

@SamCosta1 SamCosta1 commented Feb 6, 2018

Also with 2.35

@Rockster160

This comment has been minimized.

Copy link

@Rockster160 Rockster160 commented Mar 2, 2018

Also with 2.35.528157

@okunetskyi-amplify

This comment has been minimized.

Copy link

@okunetskyi-amplify okunetskyi-amplify commented Mar 7, 2018

Same issue with chrome 64.0.3282.186 and chrome driver 2.36

@yukihariguchi

This comment has been minimized.

Copy link

@yukihariguchi yukihariguchi commented Mar 27, 2018

Also with 2.36.540469

@caiopsouza

This comment has been minimized.

Copy link

@caiopsouza caiopsouza commented Apr 10, 2018

I had the same issue and noticed that if you use the param "app" when creating the driver instance the page won't load.

@pakogn

This comment has been minimized.

Copy link

@pakogn pakogn commented Apr 28, 2018

Hi!

I just faced the problem and I found a workaround.

running javascript

document.forms["formId"]["radioId"].checked=true;

this solved my problem, also with headless.

greetings!

@mattias-palm

This comment has been minimized.

Copy link

@mattias-palm mattias-palm commented Sep 14, 2018

2.42 as well. I don't know if this is the reason for the issue but it's happening on a page with an iframe. Everything inside the iframe works fine, but not on the parent outside of it.

@tomaszwojciechowski

This comment has been minimized.

Copy link

@tomaszwojciechowski tomaszwojciechowski commented Sep 20, 2018

I suggest reopening this issue.

@baash05

This comment has been minimized.

Copy link

@baash05 baash05 commented Sep 25, 2018

Seeing this issue right now.

"element not interactable\n (Session info: headless chrome=69.0.3497.100)\n (Driver info: chromedriver=2.42.591071 (0b695ff80972cc1a65a5cd643186d2ae582cd4ac),platform=Linux 4.4.0-1027-aws x86_64)\n/app/vendor/bundle/ruby/2.4.0/gems/selenium-webdriver-

@ltiritilli

This comment has been minimized.

Copy link

@ltiritilli ltiritilli commented Oct 26, 2018

It worked for me after adding:

options.addArguments("--window-size=1920,1080");
options.addArguments("--start-maximized");
options.addArguments("--headless");

@unalilker

This comment has been minimized.

Copy link

@unalilker unalilker commented Oct 31, 2018

Hi @ltiritilli,

It just worked like a charm with that arguments. (Selenium ChromeDriver 2.43.0)

Thanks a lot for your solution

@animagiq

This comment has been minimized.

Copy link

@animagiq animagiq commented Jan 25, 2019

It worked for me after adding:

options.addArguments("--window-size=1920,1080");
options.addArguments("--start-maximized");
options.addArguments("--headless");

worked for me!thx a lot

@janmohammadi

This comment has been minimized.

Copy link

@janmohammadi janmohammadi commented Jan 31, 2019

It worked for me after adding:

options.addArguments("--window-size=1920,1080");
options.addArguments("--start-maximized");
options.addArguments("--headless");

Worked for me very well! But why?!?!?!!

@mtclimberguy

This comment has been minimized.

Copy link

@mtclimberguy mtclimberguy commented Feb 6, 2019

Seeing this in Selenium ChromeDriver 2.45.615355 and Chrome 71.0.3578.98. Using in RSpec for Ruby on Rails. I can confirm that this is with a Stripe iframe on the page.

I tried adding the additional options like so, but still got the error:
Capybara.register_driver(:headless_chrome) do |app|
capabilities = Selenium::WebDriver::Remote::Capabilities.chrome(
chromeOptions: { args: %w[headless disable-gpu window-size=1920,1080 start-maximized] }
)

Capybara::Selenium::Driver.new(
app,
browser: :chrome,
desired_capabilities: capabilities
)
end

@cgoldberg

This comment has been minimized.

Copy link
Contributor

@cgoldberg cgoldberg commented Feb 6, 2019

please submit ChromeDriver issues to the Chromium project: https://bugs.chromium.org/p/chromedriver

@SeleniumHQ SeleniumHQ locked as off topic and limited conversation to collaborators Feb 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
You can’t perform that action at this time.