Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Element Send Keys is not working with Firefox 55 & geckodriver 0.18.0 #887

Closed
zhengsy741 opened this issue Aug 21, 2017 · 3 comments
Closed

Comments

@zhengsy741
Copy link

System

  • Version: 0.18.0
  • Platform: MacOS 10.12.6
  • Firefox: FF 55.0.2
  • Selenium: selenium 3.5.0

Description

When using send_keys in geckodriver 0.18.0 , it throws error as "WebDriverException: Message: Expected [object Undefined] undefined to be a string"

While the problem is resolved if i change back to geckodriver 0.17.0.

Stacktrace

File "/lib/python/site-packages/selenium/webdriver/remote/webelement.py", line 350, in send_keys
'value': keys_to_typing(value)})
File "
/lib/python/site-packages/selenium/webdriver/remote/webelement.py", line 499, in _execute
return self._parent.execute(command, params)
File "/lib/python/site-packages/selenium/webdriver/remote/webdriver.py", line 297, in execute
self.error_handler.check_response(response)
File "
/lib/python/site-packages/selenium/webdriver/remote/errorhandler.py", line 194, in check_response
raise exception_class(message, screen, stacktrace)
WebDriverException: Message: Expected [object Undefined] undefined to be a string

Trace-level log

@andreastt
Copy link
Contributor

Please provide a trace-level log, which you were asked for in the issue template but didn’t supply. It is very likely that your client is sending the wrong data format, so I’m tagging this as Selenium related.

@whimboo
Copy link
Collaborator

whimboo commented Aug 30, 2017

No response from reporter. Closing issue.

@lock
Copy link

lock bot commented Aug 17, 2019

This issue has been automatically locked since there has not been any recent activity after it was closed. If you have run into an issue you think is related, please open a new issue.

@lock lock bot locked and limited conversation to collaborators Aug 17, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants