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

Fixed compatibility with RobotFramework v2.8 #212

Closed
wants to merge 2 commits into from

Conversation

F1ashhimself
Copy link

Removed unnecessary assignment of self.current_index for compatibility with RobotFramework v2.8, in new robot version current_index is a property without setter.
You don't need to take care about None in current_index anymore if this will be true "self.current is self._no_current" it will return None by default.

Also fixed keyword.async_javascripts test for 100% passing rate.

Max Beloborodko added 2 commits June 12, 2013 16:11
…y with RobotFramework v2.8. Fixed keyword.async_javascripts test.
@pekkaklarck
Copy link
Member

Sorry for breaking backwards-compatibility with the change to ConnectionCache.current_index. I'll make it an assignable property to fix the issue on Robot side in 2.8.1:
https://code.google.com/p/robotframework/issues/detail?id=1474

Changing this in Se2Lib is probably a good idea too. It seems that Selenium2Library doesn't actually use current_index for anything, and ConnectionCache never reads it either, so the simplest fix is removing self.current_index = None altogether.

@emanlove
Copy link
Member

Fixed in #251 (without unnecessary changes async_javascript tests.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants