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

[BUG] playwright 1.15.0 causes page.goto to throw with 'Frame load interrupted' in webkit #9065

Closed
jhiesey opened this issue Sep 22, 2021 · 5 comments
Assignees

Comments

@jhiesey
Copy link

jhiesey commented Sep 22, 2021

Context:

  • Playwright Version: 1.15.0
  • Operating System: Mac and Linux
  • Node.js version: 16.9.1
  • Browser: Webkit
  • Extra: Our app uses service workers; that may or may not be relevant

Code Snippet

const { webkit } = require('playwright');

(async () => {
  const browser = await webkit.launch();
  const page = await browser.newPage();
  await page.goto('http://localhost:4000');
  // The previous line throws with
  // 'page.goto: Frame load interrupted'
})();

With playwright 1.14.1, this example worked fine. With playwright 1.15.0, page.goto rejects with 'page.goto: Frame load interrupted' only on webkit. Firefox and chromium work fine, as does the site when I load it in Safari 15.0 by hand.

Our app does use a service worker which has caused other issues with playwright in the past. I don't know if it's relevant in this case.

@jhiesey jhiesey changed the title [BUG] playwright 1.15.0 broke page.goto in webkit [BUG] playwright 1.15.0 causes page.goto to throw with 'Frame load interrupted' in webkit Sep 22, 2021
@mxschmitt
Copy link
Member

Could you try if its also reproducible for you with npm i playwright@next? Debug logs via the DEBUG=pw:protocol environment variable and/or a small repro with the web application would be helpful if you are able to track it more down. Thanks!

@jhiesey
Copy link
Author

jhiesey commented Sep 22, 2021

Installing playwright@next (1.15.0-1632328434000) still exhibits the bug.

I don't have a minimal reproduction off hand, but the bug does happen with the deployed version of the site at https://wormhole.app; i.e. with the above example changed to await page.goto('https://wormhole.app'); The public version has source maps enabled so it is debuggable.

Here is the full session running my example code in the node repl with debug logs enabled running against wormhole.app (production); the exception occurs on line 135: https://gist.github.com/jhiesey/87c387b4ecaa1059bcbaf70ad63ee63f

@jhiesey
Copy link
Author

jhiesey commented Sep 22, 2021

I can try to get a minimal reproduction if you need it, but unfortunately it's not a high priority for me at the moment and could take some time.

@yury-s
Copy link
Member

yury-s commented Sep 22, 2021

I can reproduce it locally with 'https://wormhole.app'

@mxschmitt
Copy link
Member

This is fixed in 1.15.1

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

Successfully merging a pull request may close this issue.

3 participants