New issue
Advanced search Search tips

Issue 685877 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Compat



Sign in to add a comment

Headless chromium does not render body on some pages

Reported by alexandr...@gmail.com, Jan 27 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.8 Safari/537.36

Example URL:
https://www.lemonde.fr

Steps to reproduce the problem:
1. Run `google-chrome-unstable --headless --remote-debugging-port=9222 https://www.lemonde.fr`
2. Connect to `localhost:9222` to inspect the rendered page
3. Observe a DOM with no <body> element.

What is the expected behavior?
I expect to see a rendered webpage with a body and HTML elements.
Opening the page in non-headless chrome correctly shows a body and HTML elements.

What went wrong?
The resulting DOM was not correctly computed.

Does it occur on multiple sites: N/A

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 57.0.2987.8  Channel: dev
OS Version: 
Flash Version: Shockwave Flash 23.0 r0
 
Also tested with the headless_shell example provided in the chromium repository (commit b6dc3caa93f5db4213f9e3790d469cfd841bb466), with the exact same results.
Labels: Needs-Triage-M57
Components: Blink>DOM
Labels: TE-NeedsTriageHelp
Owner: dominicc@chromium.org
Status: Assigned (was: Unconfirmed)
Cc: kenjibaheux@chromium.org
This may need a bisect--I can render this in CrOS 56.0.2924.79 (Official Build) beta (64-bit).
Labels: Proj-Headless
Cc: skyos...@chromium.org
Cc: -kenjibaheux@chromium.org
Components: Internals>Headless
Components: -Blink>DOM Blink
Labels: Needs-Bisect
Owner: ----
Status: Untriaged (was: Assigned)
Bisecting this would be a good first step. Removing the DOM component because a page could be blank in the inspector for many reasons.
Status: WontFix (was: Untriaged)
This renders fine now. I suspect the issue was that SSL certificate errors weren't being handled before.

Sign in to add a comment