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

Fix timing bug once and for all #4362

Closed
chadwhitacre opened this issue Mar 2, 2017 · 1 comment
Closed

Fix timing bug once and for all #4362

chadwhitacre opened this issue Mar 2, 2017 · 1 comment
Labels

Comments

@chadwhitacre
Copy link
Contributor

chadwhitacre commented Mar 2, 2017

#4129 #4290 #4314

@nobodxbodon at #4314 (comment):

Wow this sounds flaky. I guess there's no easy way to create some 'wait' method to listen for element change, and then verify if time elapsed isn't too long?

screen shot 2017-03-02 at 2 04 34 pm

chadwhitacre added a commit that referenced this issue Mar 25, 2017
This should squash #4362. Also:

- adapt to Firefox (`Keys.ENTER` vs `\n`)
- fix js memory leak in notifications (`delete $dialog`)
- only open one browser; reuse between classes
- git ignore geckodriver.log
chadwhitacre added a commit that referenced this issue Mar 25, 2017
This should squash #4362. Also:

- adapt to Firefox (`Keys.ENTER` vs `\n`)
- fix js memory leak in notifications (`delete $dialog`)
- only open one browser; reuse between classes
- git ignore geckodriver.log
chadwhitacre added a commit that referenced this issue Mar 25, 2017
This should squash #4362. Also:

- adapt to Firefox (`Keys.ENTER` vs `\n`)
- fix js memory leak in notifications (`delete $dialog`)
- only open one browser; reuse between classes
- git ignore geckodriver.log
@chadwhitacre
Copy link
Contributor Author

Calling this done in #4391. 🙈

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

No branches or pull requests

1 participant