[BUG] Firefox doesnt open
See original GitHub issueContext:
- Playwright Version: ^0.15.0
- Operating System: Windows
- Node version: v12.16.1.
- Browser: Firefox
const playwright = require("playwright");
async function main() {
const browser = await playwright.firefox.launch({headless:false});
const context = await browser.newContext();
const page = await context.newPage();
await page.goto("https://www.google.com");
}
main()
Using firefox doesnt work for me, it always opens a blank page and throws that error: UnhandledPromiseRejectionWarning: Error: NS_BINDING_ABORTED while navigating to https://www.google.com
When I try it with Chromium it works perfectly
Issue Analytics
- State:
- Created 3 years ago
- Reactions:9
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Firefox does not work - Common fixes to get you back up and ...
Find solutions to Firefox issues like crashing, not starting, slowness and websites not loading.
Read more >Firefox will not open at all, no matter how many times I click it.
1. Kill firefox.exe through the Task Manager, to open the taskmanager hit Win + R and enter taskmgr.exe in the window, hit enter,...
Read more >Troubleshoot and diagnose Firefox problems - Mozilla Support
1 1. Restart your computer · 2 2. Clear your cookies and cache · 3 3. Restart Firefox in Troubleshoot Mode · 4...
Read more >Firefox can't load websites but other browsers can
We'll explain errors such as "Server not found" or "Unable to connect" and how to fix problems where Firefox can't access websites but...
Read more >Firefox won't start, can't work out why - Mozilla Support
All Replies (11) · Make sure your Internet security software is up-to-date (i.e. you are running the latest version). · Remove Firefox from...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
If someone else gets the error, set a timeout of 300-400ms before getting the page and it will work
Seems like its fixed. Thanks for your work!