-
Notifications
You must be signed in to change notification settings - Fork 96
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
Send keys with shift toggle is not working for current firefox #387
Comments
I'm kind of wondering if modifier key toggling is generally supported very well. |
Hmmm... If I look at the current w3c webdriver spec for send keys, I see:
So maybe firefox is just trying to adhere to the spec. |
I do see this bug fix for firefox 99.0 (which is when behaviour changed see above). I think I'll adapt the test to include only one shift modifier. |
After I noticed firefox was failing to handle state changes for multiple key modifiers (e.g. shift key) in our ide tests, I did a little digging and decided that might be actully adhering to the w3c webdriver spec (see clj-commons#387 for details). Closes clj-commons#387
Currently
Etaoin has an ide test that exercises shift key toggling.
https://github.com/igrishaev/etaoin/blob/e8d77afec20f42be87c974ac5a09d1dbc116cb4d/resources/ide/test.side#L362-L365
The idea is this should effectively send
LOGin
.This works fine on Ubuntu on CircleCI.
But...
In local testing I found it to fail on macOS and Windows.
When things work we see log lines that look like this:
But I see failures for firefox that look like this:
It seems like the 2nd shift is not acting as a toggle.
So what's up?
I tried experimenting locally with the same Ubuntu docker image we are currently using on CircleCI. This image has the following installed:
Tests still passed when changing geckodriver to v0.29.0 and then v0.31.0 (the current release).
I then decided to bump firefox to v100.0 (current release) and saw the same failure I witnessed locally on macOS and Windows.
I did a little more testing against various versions of firefox on Ubuntu. It looks like things started to go bad in v99.
So...
I was kind of surprised that this issue seems to be in firefox and not geckodriver.
What to do?
I'm not sure, this is a pretty recent change in behavior.
One option is to temporarily adapt the test to pass for firefox and document the potential limitation.
The text was updated successfully, but these errors were encountered: