Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GridFragmentation] Basic support of break-before/break-after on item. #31825

Merged
merged 1 commit into from Dec 3, 2021

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Dec 2, 2021

This implements basic support for break-before/break-after. At the
moment it only support the top level break-before/break-after value (not
the nested values, until we set up the non-fragmented constraint space
correctly).

The break-before/break-after values are collected at the grid row level
when we calculate the grid (stored in a vector).

Currently this also doesn't (yet) search for the row with the highest
appeal.

Bug: 614667
Change-Id: I0299fa5d7b04106641903607c84fe45470f8a27c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3287251
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#947733}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

This implements basic support for break-before/break-after. At the
moment it only support the top level break-before/break-after value (not
the nested values, until we set up the non-fragmented constraint space
correctly).

The break-before/break-after values are collected at the grid row level
when we calculate the grid (stored in a vector).

Currently this also doesn't (yet) search for the row with the highest
appeal.

Bug: 614667
Change-Id: I0299fa5d7b04106641903607c84fe45470f8a27c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3287251
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#947733}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants