Running the extension inside an incognito window does not open generated report
See original GitHub issueRunning Lighthouse on a website in an incognito window, when the extension generated it opens a new tab with an URL such as blob:chrome-extension://<EXTENSION-ID>/<REPORT-ID>
. However, incognito disallows accessing this output and displays a HTTP ERROR 404 page. Consequently copying the URL back into a normal Chrome window does show the correct report.
I run Lighthouse inside an incognito window because I have other extensions running that I do not want to interfere with my performance tests.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Force install extension in incognito mode - Google Support
Open Incognito window · Find the extension, click Details · Toggle the button "Allow in Incognito" to allow the extension to run in...
Read more >Lighthouse: Unable to run generate report on localhost
Browser extensions can cause that problem. Click on the three dots under close button; Select New Incognito Window; Enter your website address ...
Read more >How to enable extensions in Incognito windows | Brave Browser
Generally, Chrome extensions won't work in Incognito mode. To enable them: Open Chrome, and click “⋮” at the top of any window or...
Read more >Chrome PDF Viewer Not Working? Here's How to Fix It
To open it, click the three dots placed in the top-right corner and select New incognito window. Or, simply press Ctrl + Shift...
Read more >Chrome Extension Troubleshooting
This page presents the most frequent reasons for which the UiPath Extension for Chrome might not work properly, and how to solve these...
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 FreeTop 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
Top GitHub Comments
This one is still open. That PR was meant for https://github.com/GoogleChrome/lighthouse/issues/1173
Bug still present in Lighthouse 2.2.1 @ Chrome 59, OSX