Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Puppeteer for Firefox should be notified on Page events (load, console, domcontentloaded...)
See original GitHub issueSteps to reproduce
Tell us about your environment:
- Puppeteer version: 0.4.2 (
puppeteer-firefox) - Platform / OS version: Ubuntu 18.04.1 LTS
- Node.js version: v10.14.1
What steps will reproduce the problem?
- Create a file named
main.jswith the following content:
main.js
const b = process.env.PUPPETEER_BROWSER || 'chrome'
const puppeteer = b === 'firefox' ?
require('puppeteer-firefox') :
require('puppeteer')
const path = require('path')
;(async function () {
const browser = await puppeteer.launch();
const page = await browser.newPage()
page.on('load', () => console.log('load'))
page.on('domcontentloaded', () => console.log('domcontentloaded'))
page.on('console', () => console.log('console'))
page.on('pageerror', () => console.log('pageerror'))
await page.goto('file://' + path.join(__dirname, 'index.html'))
await page.close();
await browser.close();
})()
- Create a file named
index.htmlwith the following content:
index.html
<!DOCTYPE html>
<html>
<head>
<title>Hello</title>
<meta charset="utf-8"/>
</head>
<body>
<script>console.log('hello')</script>
</body>
</html>
- Run the script
main.jsagainst Chrome:
node main.js
console
load
domcontentloaded
All good with puppeteer Chrome.
- Run the script
main.jsagainst Firefox
PUPPETEER_BROWSER=firefox node main.js
(empty)
What is the expected result?
First of all thanks for this amazing project! 😍 👏
Puppeteer for Firefox should trigger the following events and/or the Page should be notified:
consoleloaddomcontentloaded
I’m aware that Puppeteer for Firefox is experimental but the documentation page does list these events as “Supported API”: https://github.com/GoogleChrome/puppeteer/tree/master/experimental/puppeteer-firefox#readme
What happens instead?
No event was triggered 😐
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@msofyanqusyairi Yes, it’s documented here: https://github.com/GoogleChrome/puppeteer/pull/3657
This should work now with
puppeteer+ Firefox Nightly. If it’s still not working, feel free to reopen.