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

Fix race condition in puppeteer readyEvent #740

Merged
merged 2 commits into from
Apr 17, 2018
Merged

Conversation

KenCoder
Copy link
Contributor

Addresses #739

if (readyEvent) {
await page.evaluate(`window._readyEvent = '${readyEvent}'`)
await page.evaluate(`window._readyEvent = '${readyEvent}'`);
Copy link
Owner

Choose a reason for hiding this comment

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

I guess we are just adding this to ensure any existing dependencies are supported? We probably don't need this.

As a bonus I think it would also be nice to only enable the backstopTools log tracking if the engine is set to chromy. Not necessary to implement that bit though.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I wasn't sure why it was there in the first place, if it's not necessary they by all means delete.

I believe the PR does as you say - since I only changed puppet, the chromy path is now the only path using backstopTools.

@garris
Copy link
Owner

garris commented Apr 17, 2018

This is a very nice improvement. This was overlooked when we migrated from chromy to puppeteer. Thank you!

@garris garris merged commit 566d77c into garris:master Apr 17, 2018
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