s***@cqse.eu
2018-11-15 23:14:01 UTC
Hi everyone,
I'm using Selenium 3.13.0 with Selenium Chromedriver 2.40 on Java and I
have some key code encoding issue when sending keys to a web element. I'm
calling WebElement#sendKeys with a String that contains a URL (i.e. "Test
https://www.google.com") on a textarea element. However sendKeys seems to
press the Page-Up key instead of writing a "/". The Page-Up key is pressed
for the first "/" in the URL. The end result is the following input to the
textarea "/www.google.comTest https:". This happens because the Page-Up key
sends the cursor back to the beginning of the textarea at the first "/".
I should mention that I only have this problem on a build server (where my
test fails with the faulty input above). I myself use the default German
QUERTZ keyboard layout on my machine (where the test succeeds with the
intended input). However changing the keyboard layout to en-US or en-UK on
my machine also doesn't have the same effect as on the build server. The
test still works as intended.
I already tried a newer version of Selenium and/or the Chromedriver.
However the problem remains. Therefore I believe the problem must be
related to locale or keyboard layout. I have no idea how to proceed
debugging this issue. Any help from more experienced Selenium users is
greatly appreciated!
Best regards
Albert Steckermeier
I'm using Selenium 3.13.0 with Selenium Chromedriver 2.40 on Java and I
have some key code encoding issue when sending keys to a web element. I'm
calling WebElement#sendKeys with a String that contains a URL (i.e. "Test
https://www.google.com") on a textarea element. However sendKeys seems to
press the Page-Up key instead of writing a "/". The Page-Up key is pressed
for the first "/" in the URL. The end result is the following input to the
textarea "/www.google.comTest https:". This happens because the Page-Up key
sends the cursor back to the beginning of the textarea at the first "/".
I should mention that I only have this problem on a build server (where my
test fails with the faulty input above). I myself use the default German
QUERTZ keyboard layout on my machine (where the test succeeds with the
intended input). However changing the keyboard layout to en-US or en-UK on
my machine also doesn't have the same effect as on the build server. The
test still works as intended.
I already tried a newer version of Selenium and/or the Chromedriver.
However the problem remains. Therefore I believe the problem must be
related to locale or keyboard layout. I have no idea how to proceed
debugging this issue. Any help from more experienced Selenium users is
greatly appreciated!
Best regards
Albert Steckermeier
--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-users+***@googlegroups.com.
To post to this group, send email to selenium-***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/27113ace-6c16-46c8-a07f-6252c6a92a1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-users+***@googlegroups.com.
To post to this group, send email to selenium-***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/27113ace-6c16-46c8-a07f-6252c6a92a1f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.