Skip to content

Fixes the changed Custom Locator API - #837

Merged
aaltat merged 2 commits into
robotframework:masterfrom
aaltat:keep_custon_locator_strategy_api_2
Jun 22, 2017
Merged

aaltat merged 2 commits into
robotframework:masterfrom
aaltat:keep_custon_locator_strategy_api_2

Conversation

@aaltat

@aaltat aaltat commented Jun 22, 2017

Copy link
Copy Markdown
Contributor

Now the Custom Locator API uses the arguments:
${browser}, ${locator}, ${tag} and ${constraints}

Also moved usage of the CustomLocator to ElementFinder. And the
CustomLocator use the context for the browser.

aaltat added 2 commits June 22, 2017 23:20
Now the Custom Locator API uses the arguments:
${browser}, ${locator}, ${tag} and ${constraints}

Also moved usage of the CustomLocator to ElementFinder. And the
CustomLocator use the context for the browser.
from selenium.webdriver.remote.webelement import WebElement

from Selenium2Library.base import ContextAware
from Selenium2Library.locators.customlocator import CustomLocator

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should use from .locators import ... here.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fixed in #840

@aaltat
aaltat deleted the keep_custon_locator_strategy_api_2 branch June 22, 2017 22:36
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.

2 participants