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

Issue 593212 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Last visit > 30 days ago
Closed: Oct 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Documentation: recording a timeline - "look for the red event marker" but recording isn't live.

Reported by odelgid...@gmail.com, Mar 9 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/48.0.2564.116 Chrome/48.0.2564.116 Safari/537.36

Steps to reproduce the problem:
In its section titled "Record a page load" https://developers.google.com/web/tools/chrome-devtools/profile/evaluate-performance/timeline-tool suggests to "Stop the recording as soon as the page has finished loading (look for the red event marker)."

On my chromium, when recording timeline, the view isn't live. Rather it is greyed-out, by a modal dialogue. So I can't see the red marker, nor any other indication of events occurring through the recording.

What is the expected behavior?
I'm suspecting this might be a case of stale documentation, in the wake of resolving  crbug.com/399531 ?  crbug.com/448053   further suggests this behaviour won't change. 

I'd therefore appreciate an updated documentation on how to tell when a page 'load' event has fired, in order to stop a recording.

What went wrong?
Documentation suggests a procedure I'm unable to fulfil

Did this work before? N/A 

Chrome version: 48.0.2564.116  Channel: stable
OS Version: Ubuntu 14.04.4 LTS
Flash Version:
 
Labels: Documentation
By now I believe (through trial & error) that hitting ctrl+R in dev tools achieves the recording I'm after: i.e. it initiates a recording session, reloads the page and stops recording just after the load event is fired.

Posting this for others. If I'm correct, then such instructions would probably be good to put in the docs, instead of the existing ones.   
Labels: Te-NeedsFurtherTriage
Components: Platform>DevTools
If you look at the link you mentioned, scroll to the bottom of the page and at the left, there are two links. One is to see (and edit, if you want and submit the change) the source of the page and the other is for sending feedback.

This (Chromium) issue tracker is probably not the right place...

Comment 5 by alph@chromium.org, Jul 14 2016

Owner: kayce@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 6 by kayce@google.com, Jul 14 2016

I rewrote that doc a while ago. The section in mention no longer exists. I recommend closing this issue.
Status: Archived (was: Assigned)
Bulk DevTools triage, closing low priority issues with no action plan.

Sign in to add a comment