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

Different initial pages in different modes #2402

Closed
vsemozhetbyt opened this issue Apr 17, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@vsemozhetbyt
Copy link
Contributor

commented Apr 17, 2018

  • Puppeteer version: v1.3.0-post
  • Platform / OS version: Windows 7 x64
  • Node.js version: 10.0.0 v8-canary
(async () => {
  const browser = await require('puppeteer').launch();
  console.log((await browser.pages()).map(page => page.url()));
  await browser.close();
})();
[ 'about:blank' ]
(async () => {
  const browser = await require('puppeteer').launch({ headless: false });
  console.log((await browser.pages()).map(page => page.url()));
  await browser.close();
})();
[ 'chrome-search://local-ntp/local-ntp.html' ]

Would it be more consistent, safe and performance-wise optimal to load about:blank initially in both modes?

@aslushnikov

This comment has been minimized.

Copy link
Contributor

commented Apr 26, 2018

This sounds reasonable. We can pass default url to the args path.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.