Open
Bug 1499694
Opened 6 years ago
Updated 2 years ago
Support console.profile/profileEnd with the new performance panel
Categories
(DevTools :: Performance Tools (Profiler/Timeline), enhancement, P3)
DevTools
Performance Tools (Profiler/Timeline)
Tracking
(Not tracked)
NEW
People
(Reporter: julienw, Unassigned)
References
(Blocks 1 open bug)
Details
Currently we don't support console.profile and console.profileEnd in the new performance panel, but we'll need to support these functions before enabling it by default.
Reporter | ||
Updated•6 years ago
|
Priority: -- → P3
Comment 1•6 years ago
|
||
For what it's worth, this is a non-standard API, so I'm not particularly concerned about shipping the new performance panel without it. Safari uses it, but Chrome doesn't appear to actually record a profile with it. Chrome doesn't throw an error.
https://developer.mozilla.org/en-US/docs/Web/API/Console/profile
Reporter | ||
Comment 2•6 years ago
|
||
I'm more concerned because this would be a loss of functionality.
Now it would be nice to get some numbers about the usage of these methods.
Comment 3•6 years ago
|
||
Telemetry has USE_COUNTER2_CONSOLE_PROFILE* metrics. Numbers are super low (4 out of 30mil samples had some console.profile usage on DevEdition 62).
Comment 4•6 years ago
|
||
Chrome was also willing to remove timeline/timelineEnd in the past: https://github.com/whatwg/console/issues/27#issuecomment-288596811
Reporter | ||
Comment 5•6 years ago
|
||
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Blocks: perf-console
You need to log in
before you can comment on or make changes to this bug.
Description
•