-
Notifications
You must be signed in to change notification settings - Fork 139
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
lighthouse for current browser session #420
Conversation
It might be better if the capability was an option so it could be enabled explicitly when desired. Otherwise there is no way to get a "clean" lighthouse test with no cookies or cache populated. |
Then I assume we will need to enhance the server part to add a new option, then pass along to agents...right? |
Either an explicit option or only use this mode when a script is provided. I'm happy to plumb the test setting if you're worried about the php side of things (it's just index.php and runtest.php and can be copied from some of the other options) |
Thanks @pmeenan ! I think using this mode when a script is provided will make better sense. I will update the PR later. |
Hi @pmeenan , I had wrapped the new logic with a flag check upon task['script']. Pls help to review and proceed. Thanks! |
Hi, |
If it works that would be great to have it merged. Thank you. |
I need to double-check but I think the non-script case may also trigger it because a simple URL test is also converted into a 1-step navigate script. I think the reuse check need to check that the script length > 1 instead of > 0 |
Hi @pmeenan , |
Hi @pmeenan,
In my org, we need to test against pages behind authentication (which was identified with a cookie with max-age=session). With these changes, WPT is now able to do that (tested on Windows+Ubuntu 18.04).
Pls help to take a look whether this is something WPT wants to take in.
This might also address the issue #395