Table fragmentation wrongly reserves space for border-spacing and border
Categories
(Core :: Layout: Tables, defect)
Tracking
()
People
(Reporter: TYLin, Assigned: TYLin)
References
Details
Attachments
(6 files)
Steps to reproduce:
- Load the testcase #1 attached.
- Open print-preview.
There shouldn't be any border-spacing added to the content area at the bottom of the first page and the top of the second page.
Assignee | ||
Comment 1•11 months ago
|
||
Assignee | ||
Comment 2•11 months ago
|
||
Comment 3•11 months ago
|
||
We've got the same bug here just for border
, FWIW (no border-spacing
required). i.e. if you view the attached testcase and un-tick border-spacing
rule, Firefox still reserves space at the bottom of the first page and the top of the second page, even though we don't actually draw a table-border there.
(Chrome does not reserve that space; and we don't do that for equivalent scenarios with just blocks. So it's pretty-clearly wrong. Though it would be correct in a box-decoration-break:clone
situation.)
Assignee | ||
Updated•10 months ago
|
Assignee | ||
Comment 4•10 months ago
|
||
The testcases in our own reftest frameworks are modified to reflect the current
rendering. The main difference after this patch is that we don't apply row
spacing at the block-start edge in the table continuations.
Depends on D195332
Assignee | ||
Comment 5•10 months ago
|
||
Depends on D195333
Assignee | ||
Comment 6•8 months ago
|
||
In Part 2, we add "a" variant to exercise auto block-size on table elements.
This patch adds other variants.
- "b" variant exercises fixed block-size on table elements.
- "c" variant exercises auto block-size and
box-decoration-break:clone
on
table elements. - "d" variant exercises fixed block-size and
box-decoration-break:clone
on
table elements.
Updated•7 months ago
|
Comment 9•7 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/98473d4fe576
https://hg.mozilla.org/mozilla-central/rev/a831daee712b
https://hg.mozilla.org/mozilla-central/rev/994242ac700d
Comment 11•7 months ago
|
||
Comment 12•7 months ago
|
||
bugherder |
Updated•6 months ago
|
Comment 13•6 months ago
|
||
Reproducible on a 2024-03-05 Nightly build on macOS 12.
Verified as fixed on Firefox Nightly 126.0a1 and Firefox 125.0b4 on macOS 12, Windows 10, Ubuntu 22.
Description
•