1569821 - [css-grid] Nested grids with canvas grid-items aren't sized properly

Status: RESOLVED INVALID

(Core :: Layout: Grid, defect, P3)

Description

[u644157]

Attachment: out.png

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.100 Safari/537.36

Steps to reproduce:

I have provided an example JSFiddle here[1]. Basically, I created a grid within a grid, the inner of which containing canvas elements.

This page works fine for div elements, but not for canvases. It also shows up properly in chromium-based browsers.

[1] https://jsfiddle.net/72uvtxwj/

Actual results:

The resulting page is larger than just the viewport and hence creates scrollbars. You only see a yellow canvas, and after scrolling down for a while, you see a brown canvas.

Expected results:

The resulting page should fill the entire viewport, with no scrollbars. You should see a yellow canvas, and then a brown canvas beneath. Both should be in the viewport entirely.

Comment 1

[Pablo]

I have verified the issue and it appears on all OS and Firefox versions

Windows 10 64bit
Nightly 70.0a1 reproducible
release 68.0.1 reproducible
beta 69.0b10 reproducible

MacOS 10.14
Nightly 70.0a1 reproducible
release 68.0.1 reproducible
beta 69.0b10 reproducible

Ubuntu 18.04 64bit
Nightly 70.0a1 reproducible
release 68.0.1 reproducible
beta 69.0b10 reproducible

Comment 2

[BugBot [:suhaib / :marco]]

The priority flag is not set for this bug.
:mats, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 3

[Frank Griffith Jr]

@dholbert Is this something we can add to the upcoming Grid/Subgrid work to solve in parallel?

Comment 4

[Daniel Holbert [:dholbert]]

Chrome and WebKit actually match our behavior on this one now (giving "ACTUAL RESULTS" from comment 0), so this was probably a case where we were following the spec & others changed to match over time.

Not going into further diagnosis at this point, given the above; just resolving as INVALID since there doesn't seem to have been a bug here after all (just a behavior-difference which has been since resolved in favor of our behavior)

Comment 5

[Frank Griffith Jr]

Thanks!