Caret position in input resets

[schrotie]

I don't know if this should be considered a geckodriver problem or a chromedriver problem or whatever, but I guess the behavior should be consistent. I'm using javascript bindings, maybe its even in them ...

In geckodriver the caret will jump to the end on an input each time sendKeys is called (before actually sending the keys). In chromedriver the caret will be at the start of the input and it will stay in one place between calls.

Workaround: start key sequence with something the puts the caret where you expect it.

[christian-bromann]

This is a driver issue and should be reported in the browser driver project. This project can't fix this behavior. Let me know if you have any further questions.