-
Notifications
You must be signed in to change notification settings - Fork 9.5k
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
extension: fix 'Couldn't resolve current tab' #5885
Conversation
d9e6360
to
522950d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this avoids the issue for the URL (always using the version queried and stored when the popup first opens), but does this solve the issue of not being able to resolve the tab?
runLighthouseInExtension()
creates the ExtensionProtocol
connection, but it's not until gatherRunner.run()
-> driver.connect()
-> connection.connect()
-> _getCurrentTabId()
-> _queryCurrentTab()
that it gets the tab ID to attach to. Based on your investigation in #5668 (comment) it seems like that query would fail at that point if the user has lost access to the tab?
Maybe |
Not 100% sure what you're referring too. We fail on the first call the tabid can still be resolved just fine so that's why I did not add it as a parameter but i'm not against it. We should validate if the tabid is still available that's all, I can't think of a downside atm. |
Any progress on this @brendankenny @wardpeet ? |
@GodLesZ could you tell us which site you're auditing and what extensions you have ? |
I'm testing the chrome extension on the latest chrome (already tested on canary & stable) and always get this error. Currently we're not able to get lighthouse reports of untrusted websites, so I hope this extension is able to generate this? |
At this point, I don't think we're going to move on this :) |
Summary
bugfix
it fixes the cannot resolve tab issue in the extension

Related Issues/PRs
fixes #5668
This fix makes it easier to get this bug #5872