-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
api(context): get rid of PageEvent #1433
Conversation
src/chromium/crBrowser.ts
Outdated
const opener = target.opener(); | ||
if (!opener) | ||
return; | ||
// Opener page must have been initialized already and resumed in order to | ||
// create this popup, maybe use opener._crPage!.page()? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, we can use _initializedPage
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
On the second thought I believe there is a slight chance of race: the opener page may have been fully initialized (and resumed) in the browser but playwright didn't receive all responses yet, child page may be created and initialized before the response comes. Leaving the code as is to allow for that.
No description provided.