For anyone else experiencing this issue when running selenium webdriver in a Docker container, increasing the container size to 2gb fixes this issue. I guess this affects physical machines too if the OP fixed their issue by upgrading their server RAM to 2Gb, but could be coincidence.
You have to import it: from selenium.webdriver.common.by import By
Nice question buddy…they have written a HTTP proxy to solve the Javascript secuirty restrictions. Using this proxy made it possible to side-step many of the constraints of the “same host origin” policy, where a browser won’t allow Javascript to make calls to anything other than the server from which the current page has been served. … Read more
I got this same error: .NET WebDriver: 2.37, FF: 25.0.1. I noticed that Firefox was locking up until I exited my test application, so I built the debug version of Firefox and found that the lock-up happened when it was writing to stderr. This gave me the clue to change the webdriver code so that … Read more
( ( JavascriptExecutor ) _driver ) .executeScript( “window.onbeforeunload = function(e){};” ); solved the issue for me
HTML <div id=’a’> <div> <a class=”click”>abc</a> </div> </div> You could use the XPATH as : //div[@id=’a’]//a[@class=”click”] output <a class=”click”>abc</a> That said your Python code should be as : driver.find_element_by_xpath(“//div[@id=’a’]//a[@class=”click”]”)
This should do it! Namely you need to use action chains from webdriver. Once you have an instance of that, you simply register a bunch of actions and then call perform() to perform them. from selenium import webdriver driver = webdriver.Firefox() driver.get(“http://www.google.com”) el=driver.find_elements_by_xpath(“//button[contains(string(), ‘Lucky’)]”)[0] action = webdriver.common.action_chains.ActionChains(driver) action.move_to_element_with_offset(el, 5, 5) action.click() action.perform() This will move … Read more
I had the exact same issue. What worked for me was using the “webdrivers” gem. Part of my gemfile looks like this: group :development, :test do gem ‘rspec-rails’ gem ‘capybara’ gem ‘webdrivers’ end
As of July 2016, driver.close() and driver.quit() weren’t sufficient for me. That killed the node process but not the phantomjs child process it spawned. Following the discussion on this GitHub issue, the single solution that worked for me was to run: import signal driver.service.process.send_signal(signal.SIGTERM) # kill the specific phantomjs child proc driver.quit() # quit the … Read more