Bug: Columns not lining up with their headers if initially collapsed

JeffMercado

It seems there is a problem when dumping collections objects with multiple columns when initially collapsed to the 0th level. After expanding, all cells are rendered within the first column:

new object[]
{
    new { Foo = "foo", Bar = "bar" },
    new { A = "a", B = "b", C = "c" },
}.Dump(collapseTo: 0);

I initially thought this was for heterogeneous collections, but it looks like it happens to any collection of objects with multiple columns.

If not collapsed, it seems to render normally as expected.

Linqpad v7.4.8 (x64)
.net core 6.0.7

JoeAlbahari

I can't reproduce this. Can you provide any further clues? Can you post the HTML?

JeffMercado

Hmmm, not sure what else I can provide to you. I don't have any extensions in use here.

Host runtime version: 6.0.7
Default query runtime version: 6.0.7
Default query reference assembly version: 6.0.7
Roslyn Version: 4.4.0-1.22367.2
FSharp.Compiler.Service version: 41.0.1.0
NuGet client version: 6.1.0.106
Results rendering engine: Edge Chromium Engine 103.0.1264.77 (WebView2)

I've included my extensions and the results and assembly resolution log in this gist:
https://gist.github.com/JeffreyMercado/b4dccde0a8af8cf747ad4f8109e417e8

JoeAlbahari

Go to Edit | Preferences > Results, Style sheet for HTML results. Remove the following customization:

table[id].expandable > tbody
{
     display: table-cell;
}

JeffMercado

Ah, that did it. Didn't think that style would have affected how the html is rendered that way.

Though I don't think that was the correct value to set anyhow, I intended it to match the default style. It should have been table-row-group.

table[id].expandable > tbody
{
    display: table-row-group;
}