Closed
Bug 1816570
Opened 2 years ago
Closed 2 years ago
Named Pages do not properly handle breakpoints between out-of-flow frames
Categories
(Core :: Printing: Output, defect)
Core
Printing: Output
Tracking
()
RESOLVED
FIXED
113 Branch
| Tracking | Status | |
|---|---|---|
| firefox113 | --- | fixed |
People
(Reporter: alaskanemily, Assigned: alaskanemily)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
This is mostly an issue for floats and abspos frames.
|
Assignee | |
Updated•2 years ago
|
|
||
Updated•2 years ago
|
Severity: -- → S3
|
|
||
Updated•2 years ago
|
Component: CSS Parsing and Computation → Printing: Output
|
|
Assignee | |
Comment 1•2 years ago
|
||
The expectations in page-name-propagated-003.html have turned out to be wrong
now that we have more correct abspos support. However, this test now trips
over bug 1818596, but that affects both the test and the reference case.
We also need to check for placeholders in block reflow to actually support
named pages causing breakpoints where in-flow frames meet placeholders for out-
of-frame siblings.
|
||
Updated•2 years ago
|
Assignee: nobody → emcdonough
Status: NEW → ASSIGNED
Pushed by emcdonough@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/423fee50f9e9
Clear ReflowInput's mCanHaveClassABreakpoints for subtrees that have out-of-flow roots. r=dholbert
|
||
Comment 3•2 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox113:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 113 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•