repro 1. build headless chrome https://chromium.googlesource.com/chromium/src/+/master/headless/README.md 2. remote debug it * For screencast, you can use a url like so: http://frontend.chrome-dev.tools/serve_file/@ce6b9dfd435e967107e9677a902371864ef1bc59/inspector.html?ws=localhost:9222/devtools/page/<PAGEID>&remoteFrontend=true 3. Trace the page reload Screenshots are not captured in the trace. (However screencast does work.)
We're blocked on this over here: https://github.com/GoogleChrome/lighthouse/issues/577 Caseq, what do you think would work best? Is this something eseckler should help us with?
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/73365a379eb84bf5b54c85afe9565fc109e92809 commit 73365a379eb84bf5b54c85afe9565fc109e92809 Author: caseq <caseq@chromium.org> Date: Thu Sep 29 01:45:32 2016 Timeline: fix screenshots for headless shell Timeline relied on hard-coded name of the browser process to locate the browser main thread. This introduces a more defensive way of finding the browser in the trace. BUG= 627547 Review-Url: https://codereview.chromium.org/2378843003 Cr-Commit-Position: refs/heads/master@{#421708} [add] https://crrev.com/73365a379eb84bf5b54c85afe9565fc109e92809/third_party/WebKit/LayoutTests/inspector/tracing-browser-thread-expected.txt [add] https://crrev.com/73365a379eb84bf5b54c85afe9565fc109e92809/third_party/WebKit/LayoutTests/inspector/tracing-browser-thread.html [modify] https://crrev.com/73365a379eb84bf5b54c85afe9565fc109e92809/third_party/WebKit/Source/devtools/front_end/components_lazy/FilmStripModel.js [modify] https://crrev.com/73365a379eb84bf5b54c85afe9565fc109e92809/third_party/WebKit/Source/devtools/front_end/sdk/TracingModel.js [modify] https://crrev.com/73365a379eb84bf5b54c85afe9565fc109e92809/third_party/WebKit/Source/devtools/front_end/timeline_model/TimelineModel.js
Comment 1 by paulir...@chromium.org
, Aug 17 2016