Closed
Bug 877689
Opened 12 years ago
Closed 7 years ago
Allow blackboxing libraries when profiling
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect, P3)
DevTools
Performance Tools (Profiler/Timeline)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Gijs, Unassigned)
References
Details
(Whiteboard: [polish-backlog][difficulty=medium])
Like bug 875034, but for profiling - it's useful to be able to see which bits of your code are slow while treating the library (like the DOM code) like a black box.
|
||
Updated•11 years ago
|
Priority: -- → P4
I was about to report this bug - This would be great instead of having to drill down to find non-jQuery elements in the tree to try and find the root of the problem.
|
||
Updated•10 years ago
|
Severity: enhancement → normal
Priority: P4 → P3
|
|
||
Updated•10 years ago
|
Blocks: perf-tool-profilertree
Whiteboard: [devedition-40]
|
|
||
Updated•10 years ago
|
No longer blocks: perf-tool-profilertree
|
||
Updated•9 years ago
|
Whiteboard: [devedition-40] → [polish-backlog]
|
||
Updated•9 years ago
|
Whiteboard: [polish-backlog] → [polish-backlog][difficulty=medium]
|
||
Comment 3•7 years ago
|
||
This is done in perf.html: https://github.com/devtools-html/perf.html/pull/576
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
|
||
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•