Closed Bug 1716493 Opened 4 years ago Closed 2 months ago

New wpt failures in /css/css-grid/layout-algorithm/grid-intrinsic-size-with-orthogonal-items.html

Categories

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

defect

Tracking

()

RESOLVED DUPLICATE of bug 1977501

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 1 open bug, Blocks 2 open bugs)

Details

(Whiteboard: [wpt])

Syncing wpt PR 29299 found new untriaged test failures in CI

Tests Affected

Firefox-only failures

/css/css-grid/layout-algorithm/grid-intrinsic-size-with-orthogonal-items.html
.grid 5: FAIL

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1715435 lands.

Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.

This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/

If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.

Severity: -- → S3
Priority: -- → P3

https://wpt.fyi/results/css/css-grid/layout-algorithm/grid-intrinsic-size-with-orthogonal-items.html
http://wpt.live/css/css-grid/layout-algorithm/grid-intrinsic-size-with-orthogonal-items.html

Our failure seems to be largely or entirely that we're rendering the grid as being 1em wide, which I think is just fallout from the fact that we don't currently do a full block-direction layout pass to determine intrinsic inline-sizes (though technically we need to do so, in order to properly lay out intrinsically-sized orthogonal-flow content).

This is probably a version of bug 1310551.

Depends on: 1310551
Status: NEW → RESOLVED
Closed: 2 months ago
Duplicate of bug: 1977501
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.