starting chrome headless in repl mode gives an infinite output of {"result":{"type":"undefined"}}
Reported by
r.oussa...@gmail.com,
Jul 8 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36 Steps to reproduce the problem: 1. google-chrome --headless --disable-gpu --repl https://www.chromestatus.com/ 2. 3. What is the expected behavior? [0608/112805.245285:INFO:headless_shell.cc(278)] Type a Javascript expression to evaluate or "quit" to exit. >>> location.href {"result":{"type":"string","value":"https://www.chromestatus.com/features"}} >>> quit What went wrong? infinite output of {"result":{"type":"undefined"}} Did this work before? No Does this work in other browsers? Yes Chrome version: 59.0.3071.104 Channel: stable OS Version: 16.04 Flash Version:
,
Jul 10 2017
Issue 740407 has been merged into this issue.
,
Jul 10 2017
Thanks, I've repro this in http://www.example.com as well in versions 59 and 61.
,
Jul 17 2017
,
Jul 17 2017
I just realized that the google-chrome wrapper sanitizes the input/output of chrome, so the repl script doesn't work correctly using it.
tail /opt/google/chrome/google-chrome
# Make sure that the profile directory specified in the environment, if any,
# overrides the default.
if [[ -n "$CHROME_USER_DATA_DIR" ]]; then
# Note: exec -a below is a bashism.
exec -a "$0" "$HERE/chrome" \
--user-data-dir="$CHROME_USER_DATA_DIR" "$@"
else
exec -a "$0" "$HERE/chrome" "$@"
fi
As you said, running /opt/google/chrome/chrome should do the trick
,
Jul 17 2017
WAI |
||||
►
Sign in to add a comment |
||||
Comment 1 by r.oussa...@gmail.com
, Jul 8 2017