-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Deprecate the Lighthouse Chrome extension #8690
Comments
Extension API seemed the most straightforward. I'm not sure how to make an API private to an extension, but maybe Got a work in progress. It needs tests, and perhaps a slight consolidation of older code.
I use DevTools's |
As an extension author I would really prefer fixing the extension API to support three things |
:( |
The Chrome extension has a number of challenging issues. It's similar to DevTools as a client, but we can't have nice integration like "view trace" or "click through on node to Elements panel"
Also bugs like #4451 (distorted screenshots)
We've wanted to drop the Chrome extension for a while.
The proposal is that hitting the Browser Action icon would just immediately open DevTools Audits panel.
Implementation-wise: we'll need either protocol-level support to make this happen, an extension API that's exclusive to the LH chrome extension.
The text was updated successfully, but these errors were encountered: