Hello, is there any update on this?
On Tuesday, September 8, 2020 at 1:59:32 PM UTC-4 titusf...@gmail.com wrote:
> Yes, things just got tricky with a dev dependency I wanted to fix first
> before releasing. I'll bump this up in priority. Thanks.
>
> On Tue, Sep 8, 2020 at 10:25 AM Champ
Yes, things just got tricky with a dev dependency I wanted to fix first
before releasing. I'll bump this up in priority. Thanks.
On Tue, Sep 8, 2020 at 10:25 AM Champ wrote:
> Is there a plan to release new version of watir that allows using Selenium
> 4alpha soon?
>
> On Wednesday, September
Is there a plan to release new version of watir that allows using Selenium
4alpha soon?
On Wednesday, September 2, 2020 at 2:52:56 PM UTC-4 titusf...@gmail.com
wrote:
> Oh, except I need to release a version of Watir that allows using Selenium
> 4alpha
>
> On Wednesday, September 2, 2020 at
Thank you for the update.
On Wednesday, September 2, 2020 at 2:52:56 PM UTC-4 titusf...@gmail.com
wrote:
> Oh, except I need to release a version of Watir that allows using Selenium
> 4alpha
>
> On Wednesday, September 2, 2020 at 11:50:47 AM UTC-7 Titus Fortner wrote:
>
>> Ah, ok, this is
Oh, except I need to release a version of Watir that allows using Selenium
4alpha
On Wednesday, September 2, 2020 at 11:50:47 AM UTC-7 Titus Fortner wrote:
> Ah, ok, this is definitely a bug. Selenium 3.x is not properly handling
> the new chromium edge.
>
> You can file an issue with this
Ah, ok, this is definitely a bug. Selenium 3.x is not properly handling the
new chromium edge.
You can file an issue with this information on Selenium github tracker.
https://github.com/SeleniumHQ/selenium/issues/new?template=bug.md
The best way forward right now is to update to Selenium 4
Here is the stacktrace with selenium logging ON.
>ruby google_edge.rb
2020-09-02 10:32:12 INFO Selenium -> POST session
2020-09-02 10:32:12 INFO Selenium>>> http://127.0.0.1:17556/session |
No, I think Google is just being more backward compatible right now, which
isn't a bug for microsoft, but for the software calling a bad endpoint. So
it could be a Watir Bug.
Can you turn on the Selenium logging and show me the full log/stacktrace
for the offending section?
`Watir.logger.selenium
Thank you for the response. This works fine on chrome browser with w3c set
to true.
However, on Edge chromium if I set W3C to true, I get this error. It looks
like a bug in Edge driver?
*Backtrace:: unknown command: Cannot call non W3C standard command while in
W3C mode
Is there a reason you are setting w3c to false? (if you are testing on
Chromium > 75 you should be using w3c)
Try setting w3c to true, and if it doesn't work, try running it with
Chrome. If things are still failing, we'll have to figure out the right bug
report for the chromedriver/chromium
I am using the below code to start using Watir-webdriver with Edge Chromium
browser. I have the right versions and drivers. It launches the browser and
opens the url.
But I get the following error when I try to interact with the browser(set,
.present? etc.)
Any pointers/fixes are really
11 matches
Mail list logo
