Skip to content

Conversation

@pavelfeldman
Copy link
Member

No description provided.

@pavelfeldman pavelfeldman changed the title chore: only collect signals from top & action frames on input chore(evaluate): respect signals when evaluating on handle Mar 17, 2021
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>`);
Copy link
Member

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')),
Copy link
Member

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 ?

Copy link
Member Author

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 :/

@pavelfeldman pavelfeldman merged commit 5ae731a into microsoft:master Mar 17, 2021
YusukeIwaki added a commit to YusukeIwaki/playwright-ruby-client that referenced this pull request Mar 24, 2021
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