Closed integrii closed 7 years ago
My issue on Chrome has been flagged as 'can not reproduce' https://bugs.chromium.org/p/chromium/issues/detail?id=781634&can=2&q=headless&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified
Checking this out from more computers... perhaps my environment is broken in a very subtle and strange way?
I wasn't able to reproduce this on my second macbook. Not sure what is different between the two, but whatever it is, it breaks chrome.
It looks like something has recently broken. This docker container has been working great for a few months as a headless REPL, but now suddenly as of a few days ago pages will not render and the page content seems to be
about:blank
.I think the difference is somewhere between Chrome 61 and 64. Here is the output if I run chrome headless with a
--dump-dom
on my Mac:Here is what I get from inside the docker container as the headless user:
Note that the docker container IS able to
wget -O -
the same content as my Mac version 61, so it's not a connectivity or TLS issue of some kind.I am going to raise this in the Chrome bug reporting system, but I think we know how long that will take to get attention. In the mean time, is there a version of this container with a pinned version of Chrome?