Open
Bug 1255987
Opened 9 years ago
Updated 2 years ago
[DevTools][Memory] Incorrect description in tooltip of frame-link-filename
Categories
(DevTools :: Memory, defect, P3)
DevTools
Memory
Tracking
(firefox47 affected, firefox48 affected)
NEW
People
(Reporter: magicp.jp, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
image/png
|
Details |
frame-link-filename-tooltip.png
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
Build ID: 20160311030233
Steps to reproduce:
1. Start Nightly
2. Go to "about:home"
3. Open DevTools > Memory
4. Check-on "Record allocation stacks"
5. Reload current page
6. Switch group by to "Call Stack"
7. Take snapshot
8. Show tooltip of frame-link-filename (e.g. transport.js)
Actual results:
"View source in Debugger" is not in Debugger
Expected results:
Same with Browser Console.
Blocks: memory-frontend
Has STR: --- → yes
status-firefox47:
--- → affected
status-firefox48:
--- → affected
Component: Untriaged → Developer Tools: Memory
OS: Unspecified → All
Hardware: Unspecified → All
> Expected results:
>
> Same with Browser Console.
Browser Console was changed tooltip too...
ER: Change description to "in Debugger" or "in Browser" correctly.
|
||
Comment 2•9 years ago
|
||
It first attempts to open the source in the debugger, and if the source is not listed there, then it opens it in a new view-source:// tab.
I think we could just change this string to leave out "in <where>" completely.
Flags: needinfo?(jsantell)
Priority: -- → P3
|
||
Comment 3•9 years ago
|
||
Agreed; we could smartly change this for every viewing of source, but AFAIK we can't easily truly tell what type of file it is, so just leaving it as "view ____" is sufficient and accurate
Flags: needinfo?(jsantell)
|
||
Updated•6 years ago
|
Product: Firefox → DevTools
|
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•