-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
TypeError: string indices must be integers in selenium-py 2.49.1 #1497
Comments
Same thing with
|
Please can you create a reduced test case so I don't need to get your whole repo out and see how you build things. |
I'm not familiar enough with Selenium's internals to create a useful test case. However, it seems that the problem is, at the code here: https://github.com/SeleniumHQ/selenium/blob/master/py/selenium/webdriver/remote/errorhandler.py#L107 selenium expects |
a reduced test case is the html needed and a quick test script (this
includes what browser and everything that might be useful) to do this.
If it is not sending over JSON there is some funkiness going on.
Your bug report doesn't actually give anything meaningful to be able to
action it except a log.
|
Alright, I'll see if I can narrow down where the problem is to make a test case. |
I'm also getting this error "TypeError: string indices must be integers" on 24 tests after updating selenium after updating firefox (43.0.4). Attached is my test results - you can see in all instances of the type error, there is a click that is setting it off. |
I've ran into the same problem, here is a stripped down version of the problem: <html>
<body>
<h1>Issue 1497</h1>
<button id="button1">
<span id="span1">Click to reproduce</span>
</button>
</body>
</html> def test_issue_1497(self):
self.driver.get('file:///path/to/dev/test.html')
self.driver.find_element_by_css_selector('#span1').click() Selenium 2.49.2:
The workaround for me was to select the button element, not the span that's inside. edit2: stacktrace 2.49.2 |
I am facing this very same issue.Waiting for a fix. |
This should address the error documented here: SeleniumHQ#1497 Yes, it's ugly code.. alternatives welcome.
This should address the error documented here: #1497 Signed-off-by: AutomatedTester <david.burns@theautomatedtester.co.uk>
I'm having this issue too, glad to see there's a fix in flight... |
Project: openstack/requirements 950b5031ee73e7145ca795659ef68917ae74787a Cap Selenium package to not exceed version 2.49 Current versions of selenium package greater or equal than 2.49 contain a bug SeleniumHQ/selenium#1497 that prevents Horizon integration tests from passing. Once the fixed Selenium is released, we'll just exclude problematic versions and remove the cap. Change-Id: I9a426757b19159d9ed5ad508bf7f549015c1cdd7 Closes-Bug: #1539197
Current versions of selenium package greater or equal than 2.49 contain a bug SeleniumHQ/selenium#1497 that prevents Horizon integration tests from passing. Once the fixed Selenium is released, we'll just exclude problematic versions and remove the cap. Change-Id: I9a426757b19159d9ed5ad508bf7f549015c1cdd7 Closes-Bug: #1539197
Project: openstack/requirements 950b5031ee73e7145ca795659ef68917ae74787a Cap Selenium package to not exceed version 2.49 Current versions of selenium package greater or equal than 2.49 contain a bug SeleniumHQ/selenium#1497 that prevents Horizon integration tests from passing. Once the fixed Selenium is released, we'll just exclude problematic versions and remove the cap. Change-Id: I9a426757b19159d9ed5ad508bf7f549015c1cdd7 Closes-Bug: #1539197
Please retest in 2.50 |
2.50.0 does not fix the issue. pip freeze | grep selenium
selenium==2.50.0
|
I'm also still having this issue in 2.50 with Firefox (at least). I have the following structure:
Now, I get the error by using the following command. It's Robot code, but the traceback is identical for the Selenium-related part - except, of course, for the "find_element_by_css_selector":
Again, 2.48 works fine. |
Fixed by commit c68ace0 |
This should address the error documented here: SeleniumHQ/selenium#1497 Signed-off-by: AutomatedTester <david.burns@theautomatedtester.co.uk>
When upgrading from selenium 2.48.0 to selenium 2.49.1, I'm getting this error:
Here's the failing travis build:
https://travis-ci.org/ccnmtl/worth2/builds/103229032#L1113
And here's an example of the same exception being raised in another Django application:
https://travis-ci.org/ccnmtl/uelc/builds/103229165#L1938
The text was updated successfully, but these errors were encountered: