Closed
Bug 1613886
Opened 4 years ago
Closed 4 years ago
Move Timings and Stack Trace Panels into the right directory
Categories
(DevTools :: Netmonitor, defect, P3)
DevTools
Netmonitor
Tracking
(firefox76 fixed)
RESOLVED
FIXED
Firefox 76
| Tracking | Status | |
|---|---|---|
| firefox76 | --- | fixed |
People
(Reporter: Honza, Assigned: bomsy)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
image.png
The Timings, Cache and Stack Trace panels should be moved into a new request-details directory.
Honza
|
Reporter | |
Updated•4 years ago
|
Summary: Move Timings and Cache Panels into the right directory → Move Timings, Cache and Stack Trace Panels into the right directory
|
|
Reporter | |
Comment 1•4 years ago
|
||
The Stack Trace panel could perhaps deserve some some UI polish (done as part of this bug).
|
|
Reporter | |
Comment 2•4 years ago
|
||
From Victoria (on Slack)
Seems like link styling is a bit misleading given the behavior of opening the sidebar instead of going to another panel, etc. However, if it seems good to call this out, we could give it the darkblue:blue syntax highlighting used in various places including the stack traces panel
|
Assignee | |
Updated•4 years ago
|
Summary: Move Timings, Cache and Stack Trace Panels into the right directory → Move Timings and Stack Trace Panels into the right directory
|
|
Assignee | |
Comment 3•4 years ago
|
||
|
||
Updated•4 years ago
|
Assignee: nobody → hmanilla
Status: NEW → ASSIGNED
|
|
||
Updated•4 years ago
|
Attachment #9131768 -
Attachment description: Summary: moved the timings and stacktrace panels to /requst-details → Bug 1613886 - Moved the timings and stacktrace panels to /requst-details r=honza
Pushed by hmanilla@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/70f10de8eecc Moved the timings and stacktrace panels to /requst-details r=Honza
|
||
Comment 5•4 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox76:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 76
You need to log in
before you can comment on or make changes to this bug.
Description
•