The remote end steps of Element Send Keys requires us to handle specific elements differently. Those steps haven't been added yet. https://w3c.github.io/webdriver/webdriver-spec.html#element-send-keys > 10. Run the substeps of the first matching condition: * element is an input element whose type attribute is File. * The user agent renders element as something other than a text input control (for example an input element in the color state being presented as a colorwheel): * element is content editable
Similarly there are a few other “HTML5” form controls we need to handle, such as <input type=color>. We already handle <input type=date> and <input type=time> through interaction.setFormControlValue.
Priority: -- → P2
Summary: Add support to Send Keys for special elements (date, file, contenteditable) → Add support to Element Send Keys for <input type=date> and <input type=color>
Hm, we already have that code in place for content: https://dxr.mozilla.org/mozilla-central/rev/cad9c9573579698c223b4b6cb53ca723cd930ad2/testing/marionette/listener.js#1411 What we should do is clearly to move the call of `setFormControlValue()` to after the interactability checks as being worked on in bug 1414322. Otherwise not sure yet what else is broken.
Depends on: 1414322
OS: Unspecified → All
Hardware: Unspecified → All
Version: 56 Branch → Trunk
Summary: Add support to Element Send Keys for <input type=date> and <input type=color> → WebDriver:SendKeysToElement support for <input type=date> and <input type=color>
You need to log in before you can comment on or make changes to this bug.