Closed
Bug 1870906
Opened 1 year ago
Closed 1 year ago
Refactor nsGridContainerFrame::ComputeSelfSubgridMasonryBits()
Categories
(Core :: Layout: Grid, task)
Core
Layout: Grid
Tracking
()
RESOLVED
FIXED
123 Branch
Tracking | Status | |
---|---|---|
firefox123 | --- | fixed |
People
(Reporter: dholbert, Assigned: dholbert)
References
Details
Attachments
(2 files)
Filing this bug for some supporting refactoring to prepare for bug 1800563's fix.
Assignee | ||
Comment 1•1 year ago
|
||
This patch doesn't change behavior; it's just refactoring out some
existing checks into a helper function.
Depends on D196900
Updated•1 year ago
|
Attachment #9369512 -
Attachment description: Bug 1870906 part 2: Split out a helper function to determine whether a grid can't form a subgrid due to being an independent formatting context. r?TYLin → Bug 1870906 part 2: Split out a helper function to determine whether we should inhibit a grid from being a subgrid. r?TYLin
Assignee | ||
Comment 2•1 year ago
|
||
This patch doesn't change behavior.
The code that follows the new early-return is all in the service of making
changes to the return value bits
; and all of the modifications are guarded
directly or indirectly by checks for !inhibitSubgrid
. So we might as well
just morph this inhibitSubgrid
variable into an early-return and skip all of
that code entirely when it evaluates to true.
Pushed by dholbert@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/482dff4d6dbe
part 1: Simplify ComputeSelfSubgridMasonryBits() to return early once we know we can't be a subgrid. r=TYLin,emilio
https://hg.mozilla.org/integration/autoland/rev/038afa747b43
part 2: Split out a helper function to determine whether we should inhibit a grid from being a subgrid. r=TYLin
Comment 4•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/482dff4d6dbe
https://hg.mozilla.org/mozilla-central/rev/038afa747b43
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox123:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•