New issue
Advanced search Search tips

Issue 706577 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

DevTools: console.table incorrectly shows empty cells when some rows have 1000+ properties

Project Member Reported by l...@chromium.org, Mar 29 2017

Issue description

Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

What steps will reproduce the problem?
(1) Enter this in the DevTools console:
`
var a = [];var b = [];
var max = 2000;
for (var i=0; i < max; i++) {
    a[i*max/20] = 1;
	b[i*max/20] = 1;
	b[i] = 1;
}
console.table([a,b]);
`
(2) See the resulting table with column names with increments of 100

What is the expected result?
Both rows should have 1's filled in all the cells.

What happens instead?
The 2nd row has 1's for only the first half of its columns.


Injected script source's preview logic says to generate up to 1000 properties for each row, which the inspector frontend then uses to generate columns.  If some objects have 1000+ properties, we may miss out on their values in later columns.
 

Comment 1 by obooc...@gmail.com, Jul 20 2017

I find that in chrome console.table broken and just output an empty row. 

MacOS 10.12.5 (16F73)
Chrome Version 59.0.3071.115 (Official Build) (64-bit)
Screen Shot 2017-07-20 at 10.03.49 AM.png
21.3 KB View Download

Comment 2 by l...@chromium.org, Jul 20 2017

@Comment 1, thanks for the screenshot, I believe that bug has been filed separately in:  https://crbug.com/663878 

That bug where shallow arrays `console.table([1,2])` just show nothing already has a fix.  It should be currently working on Chrome Beta and Canary channels, and will be live on stable Chrome in the near future.

Comment 3 by l...@chromium.org, Dec 5 2017

Status: WontFix (was: Assigned)
Closing for now since this is a rare case that requires more than frontend changes.

Sign in to add a comment