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

Issue 757278 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit 17 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Update Headless Chrome starting guide with Mac/Windows in mind

Project Member Reported by dvallet@chromium.org, Aug 21 2017

Issue description

The starting guide: https://developers.google.com/web/updates/2017/04/headless-chrome
is a great place where new users start playing with Headless Chrome. 

The guide was written when only linux support was offered though so some users are finding problems when trying on Mac/Windows. Some examples: 

-  https://crbug.com/749208 
- https://crbug.com/753439
-  https://crbug.com/740343 
-  https://crbug.com/740407 

The main problems i've found so far are: 
- Using default output for screenshot and print-to-pdf: This can give problems in Windows since it runs on the executable directory, which sometimes users have no permissions to write
- dump-dom and commands that write to stdout don't work in Windows unless --enable-logging is provided, even if this is provided the standard executable in Windows may also block stdout 
- --repl is not supported in Windows, due to the avobe issues.
- --repl can also give problems in all platforms if run through the default binary (script), see  https://crbug.com/740343 


 
Sure, I can add these gotchas. It's mainly just the notes on Windows?
Thanks! Yes I think most of the problems are with Windows and --repl not working properly when used with the google-chrome executable wrapper

Sign in to add a comment