Issue metadata
Sign in to add a comment
|
Cookies not saved in headless mode |
||||||||||||||||||||||
Issue descriptionTo reproduce: $ cr run headless_shell --user-data-dir=/tmp/testing --screenshot https://jsfiddle.net/6wzn6vwo/ && xdg-open screenshot.png (Repeat 2x -- second screenshot should show cookie from earlier run)
,
Jul 5 2017
It would be really nice if you could manually choose an existing Chrome profile when using "--headless", currently you cannot.
,
Jul 5 2017
@johnbarr, All chrome profiles are stored on disk. You can see the exact profile path you're currently using on `about:version`. You can pass that path to `--user-data-dir=` to use it.
,
Jul 5 2017
paulirish@ Yupp, I am aware of the --profile-directory and --user-data-dir params, but they don't seem to work with headless chrome. My repro case is below: On version Version 60.0.3112.50 of chrome: $ google-chrome-beta --profile-directory="Profile 2" "--user-data-dir=.config/google-chrome-beta/" will correctly open that profile, which is signed into a google account However the following: $ google-chrome-beta --headless --disable-gpu --profile-directory="Profile 2" "--user-data-dir=.config/google-chrome-beta/" --screenshot http://accounts.google.com will produce the attached screenshot, which is not signed into a google account.
,
Jul 21 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by skyos...@chromium.org
, May 15 2017