Python client keys_to_typing no longer handles non-string iterable #1839
Comments
joshbruning
referenced
this issue
Mar 18, 2016
file_detector_context and custom file_detector * You can pass custom file_detector right in the constructor, default behaviour is unaltered. * file_detector_context context manager to safely change file detectors in limited contexts. Signed-off-by: Luke Inman-Semerau <luke.semerau@gmail.com>
lukeis
pushed a commit
that referenced
this issue
Mar 28, 2016
keys_to_typing handles list of Keys. keys_to_typing behavior was regressed by an implementation change. This change reverts keys_to_typing to its former behavior. That is, element.send_keys([Keys.ENTER]) should result in the ENTER key being pressed, not the unicode representation of ENTER defined in common/keys.py to be typed into a text field. Fixes #1839 Signed-off-by: Luke Inman-Semerau <luke.semerau@gmail.com>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
d095cd2
regressed keys_to_typing in the Python client.
Expected Behavior -
Send list [Keys.ENTER], results in enter key press.
Actual Behavior -
Send list [Keys.ENTER], results in "[u'\ue007']" sent to a text box.
The text was updated successfully, but these errors were encountered: