Closed
Bug 1405250
Opened 7 years ago
Closed 2 years ago
Migrate browser_webconsole_closure_inspection.js to the new frontend
Categories
(DevTools :: Console, defect, P3)
DevTools
Console
Tracking
(firefox57 wontfix, firefox58 affected)
RESOLVED
INACTIVE
People
(Reporter: nchevobbe, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: [newconsole-reserve])
Attachments
(1 file)
59 bytes,
text/x-review-board-request
|
Details |
migrate variableview test to objectinspector
Reporter | ||
Updated•7 years ago
|
status-firefox57:
--- → wontfix
Priority: -- → P3
Reporter | ||
Updated•7 years ago
|
Assignee: nobody → nchevobbe
Status: NEW → ASSIGNED
Reporter | ||
Comment 1•7 years ago
|
||
The old test was testing that we had a `<Closure>` node in the VariablesView. This node is handled here https://searchfox.org/mozilla-central/rev/9bab9dc5a9472e3c163ab279847d2249322c206e/devtools/client/shared/widgets/VariablesViewController.jsm#440-481.
We don't have that at the moment in the ObjectInspector, and I am not sure we should migrate this feature ?
Reporter | ||
Comment 2•7 years ago
|
||
This was added in Bug 810966, at the same time than in the debugger if I understand correctly, where the VariableView was used as well. Following https://bugzilla.mozilla.org/show_bug.cgi?id=810966#c1 STR, I don't see it in the debugger as well.
Jason, Yulia, do you think we should add that in both console and debugger ?
Comment hidden (mozreview-request) |
Reporter | ||
Comment 4•7 years ago
|
||
Added a patch that migrate the test but fail (and does not test the "<Closure>" node)
Updated•7 years ago
|
Priority: P3 → P1
Whiteboard: [newconsole-mvp]
Updated•7 years ago
|
Assignee: nchevobbe → nobody
Status: ASSIGNED → NEW
Priority: P1 → P3
Whiteboard: [newconsole-mvp] → [newconsole-reserve]
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•2 years ago
|
Severity: normal → S3
Reporter | ||
Comment 5•2 years ago
|
||
closing, we'll add proper test if and when we do Bug 1443848
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•