Send keys should be implemented using the actions API as per spec
Project Member Reported by firstname.lastname@example.org, Sep 8 2017
spec: https://w3c.github.io/webdriver/webdriver-spec.html#element-send-keys Note that this is currenlty blocked on: https://bugs.chromium.org/p/chromedriver/issues/detail?id=1897
Jan 22 2018,
I apologise for the noise... I am writing a webdriver library, and noticed that while the specs seem to indicate that the keys to be inserted should be a string in the `text` argument, Chromedriver seems to expect an `Array` in the `value` argument. The specs indicate: * Let text be the result of getting a property text from the parameters argument. Is this something that will be addressed?
Is there any sensible way to work around this? The legacy protocol only has a "send keys to the currently active element" command, and I can't see any sane way to change the currently active element when starting from a web element reference. This is currently the only issue I can't workaround in https://github.com/web-platform-tests/wpt/pull/12380 to remove the Selenium indirection in the wptrunner test execution.
Oh, wait, I'm just misreading the old JSON wire protocol docs; https://github.com/SeleniumHQ/selenium/wiki/JsonWireProtocol#sessionsessionidelementidvalue works fine for this.
Sign in to add a comment