[Webkit-unassigned] [Bug 86272] New: Web Inspector: "Load timeline data" should be future proof
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri May 11 16:25:54 PDT 2012
https://bugs.webkit.org/show_bug.cgi?id=86272
Summary: Web Inspector: "Load timeline data" should be future
proof
Product: WebKit
Version: 528+ (Nightly build)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: Web Inspector
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: tonyg at chromium.org
CC: timothy at apple.com, rik at webkit.org, keishi at webkit.org,
pmuellr at yahoo.com, joepeck at webkit.org,
pfeldman at chromium.org, yurys at chromium.org,
bweinstein at apple.com, apavlov at chromium.org,
loislo at chromium.org
Due to bug 86254, I had to use an old copy of Chrome 15 to load timeline data recorded with Chrome 20.
However, the old version wouldn't load the new trace because it included type: "BeginFrame" events which it didn't understand. So it throws:
[17846:263:70980640361484:ERROR:CONSOLE(50564)] "Uncaught TypeError: Cannot read property 'category' of undefined", source: chrome-devtools://devtools/DevTools.js (50564)
[17846:263:70980640449015:ERROR:CONSOLE(51079)] "Uncaught TypeError: Cannot read property 'name' of undefined", source: chrome-devtools://devtools/DevTools.js (51079)
It would be nice if the code were written so that unknown types are ignored. This will avoid breaking compatibility when we add types in the future.
As a workaround, I manually removed the BeginFrame events from the JSON.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list