Closed Bug 1987958 Opened 10 months ago Closed 9 months ago

Determine position fallback based on basic `flip-*` keywords

Categories

(Core :: CSS Parsing and Computation, enhancement)

enhancement
Points:
3

Tracking

()

RESOLVED FIXED
145 Branch
Tracking Status
firefox145 --- fixed

People

(Reporter: dshin, Assigned: emilio)

References

()

Details

(Whiteboard: [anchorpositioning:m2])

Attachments

(2 files)

No description provided.

For reference, the flip-* syntax here is:
<try-tactic> = flip-block || flip-inline || flip-start

Points: --- → 3
Whiteboard: [anchorpositioning:triage] → [anchorpositioning:m2]
Assignee: nobody → emilio
Status: NEW → ASSIGNED
Depends on: 1924086

This implements an initial version of position-try-fallback, that
supports only <position-area> and <position-try-tactic> applied to
position area.

Lot's of follow-up work to do, like:

  • Applying <position-try-tactic> to margins / paddings / etc.
  • @position-try (not too hard)
  • Figure out what to do if the abspos should fragment.

But still probably worth landing this.

The checks for fragmentation I think want to use the original containing
block rect.

Using that rect for GetLogicalSize doesn't matter because we already force
kidNeedsReflow = true for orthogonal kids.

This is useful because we're going to need to reflow children multiple
times for position-try.

Blocks: 1991333
Duplicate of this bug: 1987959
Duplicate of this bug: 1987956
Status: ASSIGNED → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → 145 Branch
QA Whiteboard: [qa-triage-done-c146/b145]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: