Closed
Bug 1332011
Opened 8 years ago
Closed 8 years ago
Investigate usage of reps/object inspector in new webconsole
Categories
(DevTools :: Console, defect, P2)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1308566
People
(Reporter: jdescottes, Unassigned)
Details
For the new console frontend, we want to use debugger.html object inspector to replace the variables view.
We will use the object inspector when logging objects, so that we can expand them and see their content from inside the console. But what about simpler types of objects, such as strings, numbers etc...
Is the object inspector able to render primitive types? If not should, should it be able to do so?
If the object inspector becomes some kind of UI component for reps, should it move to the reps repository? This way it would be delivered to mc through the reps bundle.
Otherwise what's the plan to retrieve it and use it in the console?
The goal of this bug is to define the usage of object inspector in the console, as well as how we will integrate it. New console frontend features that rely on using the Object Inspector should use this bug as blocker.
Updated•8 years ago
|
Flags: qe-verify-
Priority: -- → P2
Summary: [meta] Investigate usage of reps/object inspector in new webconsole → Investigate usage of reps/object inspector in new webconsole
Whiteboard: [new-console]
Updated•8 years ago
|
Priority: P2 → P1
Comment 1•8 years ago
|
||
In the netmonitor, we use the tree-table component, which may be a better fit.
Updated•8 years ago
|
Priority: P1 → P2
Comment 2•8 years ago
|
||
I think this is a dup.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
Updated•8 years ago
|
No longer blocks: enable-new-console
Whiteboard: [new-console]
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•