Closed
Bug 1067710
Opened 11 years ago
Closed 6 years ago
console.table() column limit should match Chrome's
Categories
(DevTools :: Console, defect, P2)
Tracking
(firefox72 fixed)
RESOLVED
FIXED
Firefox 72
Tracking | Status | |
---|---|---|
firefox72 | --- | fixed |
People
(Reporter: u443210, Assigned: nchevobbe)
References
Details
(Whiteboard: [polish-backlog])
Attachments
(1 file)
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:35.0) Gecko/20100101 Firefox/35.0
Build ID: 20140915030204
Steps to reproduce:
-Open the web console.
-Copy and paste this:
foo = {
bar1: {
prop1: 1,
prop2: 2,
prop3: 3,
prop4: 4,
prop5: 5,
prop6: 6,
prop7: 7,
prop8: 8,
prop9: 9,
prop10: 10,
prop11: 11,
prop12: 12,
prop13: 13,
prop14: 14,
prop15: 15,
prop16: 16,
prop17: 17,
prop18: 18,
prop19: 19,
prop20: 20
},
bar2: {
prop1: 1,
prop2: 2,
prop3: 3,
prop4: 4,
prop5: 5,
prop6: 6,
prop7: 7,
prop8: 8,
prop9: 9,
prop10: 10,
prop11: 11,
prop12: 12,
prop13: 13,
prop14: 14,
prop15: 15,
prop16: 16,
prop17: 17,
prop18: 18,
prop19: 19,
prop20: 20
}
}
console.table(foo)
Actual results:
The max number of columns displayed is 10.
Expected results:
Should not have a limit number of columns.
Comment 1•11 years ago
|
||
+1. I know this is a newer feature for dev tools, but limiting the number of columns makes it really confusing if you're inspecting an object with more properties than that limit, with no indication that there are more properties on the object than are enumerated in the table.
Updated•10 years ago
|
Whiteboard: [p
Updated•10 years ago
|
Whiteboard: [p → [polish-backlog]
Updated•9 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Comment 2•8 years ago
|
||
I wonder what the correct behavior would be.
Also I note that Chrome allows 20 columns.
For the new console the value seems readily changed, but my naive attempt did not immediately work.
https://dxr.mozilla.org/mozilla-central/rev/e03e0c60462c775c7558a1dc9d5cf2076c3cd1f9/devtools/client/webconsole/new-console-output/components/console-table.js#19
Comment 3•8 years ago
|
||
Ideally, text in the table cells can wrap to more than one line (which could leave room for more columns, and fixes the problem of content being cut off with no way to access the cell contents).
Alternatively just show the first X characters of each cell, and show the full cell content when the content is clicked.
Updated•7 years ago
|
Product: Firefox → DevTools
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → nchevobbe
Status: NEW → ASSIGNED
Summary: console.table() should not have a limit number of columns. → console.table() column limit should match Chrome's
Assignee | ||
Comment 4•6 years ago
|
||
Increasing the number of columnns highlighted some issues:
- Some element could be off-screen, the grid-template-columns
needed to be adjusted - headers could be cut-off, we add a title on the element to
have the full content in a tooltip - properties that are not defined were displayed as "undefined",
which is not really true, and take a lot of space. We render
them as an empty cell in such case now.
A test is added to check the max-column limit.
Depends on D53962
Pushed by nchevobbe@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6e0c4b949057
Bump console.table columns limit to 21 to match Chrome. r=Honza.
Comment 6•6 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox72:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 72
Updated•6 years ago
|
QA Whiteboard: [qa-72b-p2]
You need to log in
before you can comment on or make changes to this bug.
Description
•