Replies: 1 comment
-
You can use a file instead:
This will let you ignore any escaping needed for your terminal, and just store the values in a plain json object. Other approaches, FYI: https://github.com/GoogleChrome/lighthouse/blob/main/docs/authenticated-pages.md |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How can I add the right cookies to pre-accept a cookiebot popup? I don't really want to test that part.
I've already tried:
And that is identical to a real browser having accepted it, where the popup no longer shows. But it's not working. It's either ignored, or it's wrong. It's difficult to test, as within 10 seconds or so the lighthouse browser disappears again. It's very possible that some character gets interpreted differently, like the
%
ones in there. But I have no way of knowing.On a sidenote: why does it have to be json? That doesn't make any sense on the CLI, what with the (double) encoding going on.
(edit: does it have to json, actually?
--help
doesn't say what kind of format is expected, and so this is just something I found buried in examples floating around)So anyway, what is the correct way to achieve what I want? Perhaps forcing that cookie isn't even it.
Beta Was this translation helpful? Give feedback.
All reactions