Skip to content
This repository has been archived by the owner on Feb 18, 2021. It is now read-only.

Should be aware of control flow deprecation #329

Closed
manoj9788 opened this issue Nov 25, 2016 · 4 comments
Closed

Should be aware of control flow deprecation #329

manoj9788 opened this issue Nov 25, 2016 · 4 comments
Assignees
@Stojdza
Labels
OSS Citizen [Type] Task

Comments

@manoj9788
Copy link
Contributor

Just raising this, work on changing parts where control flow is used. If you guys are already aware and have plans to change we can close this.
SeleniumHQ/selenium#2969
@hoverduck
Copy link
Contributor

Thanks @manoj9788....Selenium 3.0.0 is on my radar, but I hadn't actually spent much time looking at the new async stuff yet. We'll leave this issue open to make sure it's on our minds as we move forward.

cc: @alisterscott

@manoj9788
Copy link
Contributor Author

manoj9788 commented Nov 30, 2016 •
edited
Loading

@hoverduck Sure, am happy to help. I will soon put a new repository on the new async showcasing a demo.

@alisterscott
Copy link
Contributor

We probably need to prioritize this now that we're on Node 8.9.x

@alisterscott
Copy link
Contributor

We should move to using async/wait: https://github.com/SeleniumHQ/selenium/wiki/WebDriverJs

@igladun igladun self-assigned this Feb 16, 2018
@brbrr brbrr mentioned this issue Mar 8, 2018
Closed
@alisterscott alisterscott assigned Stojdza and unassigned igladun Jun 22, 2018
@alisterscott alisterscott mentioned this issue Jun 22, 2018
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Stojdza Stojdza

Labels
OSS Citizen [Type] Task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@alisterscott @manoj9788 @igladun @Stojdza @hoverduck @matticbot