New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 753118 link

Starred by 9 users
Status: Assigned
Owner:
█ lushnikov@chromium.org
Last visit 29 days ago
Cc:
dgozman@chromium.org
█ dvallet@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

DevTools: Page.printToPDF should work in non-headless mode

Project Member Reported by lushnikov@chromium.org, Aug 7 2017 
Chrome Version: 59

Page.printToPDF should work in non-headless mode: protocol should be functionable in both headless and non-headless modes.

Comment 1 by dgozman@chromium.org, Aug 8 2017

Cc: dvallet@chromium.org
Labels: -Pri-3 OS-All Pri-2
Owner: jzfeng@chromium.org
Status: Assigned (was: Untriaged)
Preemptively assigning to jzfeng@. We should wire this up in content/ to support in non-headless mode.
See example on how this was done for dialogs: https://chromium-review.googlesource.com/c/592608.
In this case we can intercept IPCs in content instead of headless, or expose API between content/ and components/printing, or inject a protocol-based handler (through components/printing API) from ChromeDevToolsManagerDelegate.

Comment 2 by pfeldman@chromium.org, Dec 14 2017

Owner: lushnikov@chromium.org

Comment 3 by lucasngu...@gmail.com, Dec 3 

Hi,
I am using Page.printToPDF in a production scenario.
Sometimes we need to manually change between headless and non-headless modes due this bug.
Would be very helpful to run our tests in non-headless mode.
Do you have any schedule for this?
Thanks.
►

Sign in to add a comment