Tired of filling out web forms with the same information time and time again? Autofill lets you complete forms with just one click. Choose from results and suggestions that appear as you type, including your recent searches and visited websites, so you can get to what you want in a snap. Is this an oversight on their part, or does v2.Search and navigate from the same box. Is that normal? I certainly wasn't expecting it to say v2.2, but there are no other versions apart from 2.8 installed by brew (so I doubt brew is accidentally using the older version), and when I run the file I downloaded directly, I'm quite sure it's version 2.8 from the Chromedriver website. I'm certain they are both in fact version 2.8, but when I launch either one the console says: Starting ChromeDriver (v2.2) on port 9515
Side Question: After downloading chromedriver 2.8 directly and also installing it with brew, I tried launching both the downloaded version and the brew version separately to confirm that either version could launch successfully. Can anyone confirm that I've done what one normally does to set up the chromedriver? Unfortunately, my issue is still unresolved. As far as I understand it, this should allow my automation to detect and launch the chromedriver. My PATH contains /usr/local/bin, which has a chromedriver link to the location brew installed to. usr/local/Cellar/chromedriver/2.8 (2 files, 21M) * brew info chromedriver now yields: chromedriver: stable 2.8 I became skeptical that the version in my Downloads directory was the version that was being used in the first place, so I used brew to install it. I tried replacing this file with version 2.8 from here, but it had no effect. I had a version of chromedriver sitting in my Downloads directory that I thought my code was referring to, but I couldn't find my Downloads directory in the PATH (I'm using OS X by the way).
Figuring out what version of chromedriver I had been using actually turned out to be more difficult. So I've updated selenium-webdriver to 2.39.0. 77 on January 14, that seemed like good solid evidence to me. Googling around revealed that this was likely caused by an out-of-date chromedriver or selenium-webdriver, which sounded very plausible, since neither had been updated in a long time (I think chromedriver was at 2.2 and selenium-webdriver was at 2.35.1), and since Chrome auto-updated to. I'm seeing Selenium::WebDriver::Error::UnknownError: unknown error: unable to discover open pages I came in to the office yesterday morning to find that my Capybara tests couldn't interact with Chrome.
0 kommentar(er)
