chrome://tracing broken -> Polymer is not defined
Reported by
jer...@duckware.com,
Jul 26 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2807.1 Safari/537.36 Steps to reproduce the problem: 1. run latest Win canary 2. go to chrome://tracing 3. nothing appears What is the expected behavior? What went wrong? F12 console shows: Uncaught ReferenceError: Polymer is not defined Did this work before? Yes Chrome version: 54.0.2807.1 Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 22.0 r0
,
Jul 26 2016
,
Jul 26 2016
That CL is supposed to fix the problem that you mentioned. I just build Chrome locally on linux & about://tracing works. Can you do "git pull" & "gclient sync", and build Chrome again?
,
Jul 26 2016
Confirmed that syncing fixes this. I must have got in too early this morning and just missed your patch.
,
Jul 27 2016
Issue 630926 has been merged into this issue.
,
Jul 27 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/a6c428bad618519ab8c696f697a4208022c6d9b3 commit a6c428bad618519ab8c696f697a4208022c6d9b3 Author: nednguyen <nednguyen@google.com> Date: Wed Jul 27 16:11:28 2016 [tools/perf] Add integration test for about://tracing UI BUG= 631812 , 631535 , 630030 Review-Url: https://codereview.chromium.org/2189603002 Cr-Commit-Position: refs/heads/master@{#408143} [add] https://crrev.com/a6c428bad618519ab8c696f697a4208022c6d9b3/tools/perf/core/about_tracing_integration_test.py |
||||
►
Sign in to add a comment |
||||
Comment 1 by pdr@chromium.org
, Jul 26 2016Owner: nednguyen@chromium.org
Status: Untriaged (was: Unconfirmed)