-
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
chore(evaluate): respect signals when evaluating on handle #5847
Conversation
it('should work with noWaitAfter: true', async ({page, server}) => { | ||
server.setRoute('/empty.html', async () => {}); | ||
await page.setContent(`<a href="${server.EMPTY_PAGE}">empty.html</a>`); | ||
await page.setContent(`<a id="anchor" href="${server.EMPTY_PAGE}">empty.html</a>`); |
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.
Revert this and the one below?
const frame = page.frame({ name: 'target' }); | ||
await Promise.all([ | ||
page.click('a').then(() => messages.push('click')), | ||
page.waitForEvent('framenavigated').then(() => messages.push('navigated')), |
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.
can we have a test that checks that we don't wait for the frame navigation ?
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.
It might be tricky - we would need to simulate slow iframe navigation commit :/
No description provided.