Table cells (td) with rowspan are split between pages
Reported by
nowak2...@poczta.onet.pl,
Sep 10 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 Example URL: https://jsfiddle.net/gmpfo05q/6/ Steps to reproduce the problem: 1. Open the JsFiddle provided. 2. Click on the Print button to open the Print Preview window. What is the expected behavior? In the first column, the last cell on the page (with rowspan) should remain on one page (together with its cells in four rows on the right). What went wrong? The last cell on the page is split between to other pages, and it doesn't stay aligned with 4 rows (rowspan=4) it is meant to stick with. Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? No Firefox 55.0.2 Chrome version: 60.0.3112.113 (Developer Build) Built on Ubuntu , running on Ubuntu 17.04 (64-bit) Channel: stable OS Version: Ubuntu 17.04 Flash Version: Shockwave Flash 26.0 r0
,
Sep 11 2017
,
Sep 11 2017
Didn't this work before? See commit https://codereview.chromium.org/2412923002 and other commits in the table code by me around October 2016. This was an intentional change. This is because vertical alignment and pagination are essentially incompatible. If we detect that a cell will cross fragmentainer boundaries, we'll ignore vertical alignment properties and top-align everything. This is similar to what Edge does.
,
Sep 11 2017
The bug is about splitting a "rowspanning" cell (also styled with "page-break-inside: avoid", AFAIK ignored anyway) between pages.
,
Sep 11 2017
Splitting a cell (rowspanned or not) between pages is allowed, but, yes, if break-inside:avoid is specified, we should really try to avoid it. Looks like we fail at that, regardless of rowspan. That's the only bug I can see here. Attaching a test case, which uses multicol instead of printing.
,
Sep 11 2017
The repro in comment 5 doesn't seem to specify break-inside:avoid?
,
Sep 11 2017
Though it is indeed broken in the fashion you describe even with break-inside:avoid https://jsfiddle.net/dgrogan/xsqv4z4s/
,
Sep 11 2017
Yes, that's what I meant! :) Thanks for noticing the mistake.
,
Sep 13 2017
,
Nov 27 2017
I do not know if this is the same issue or another. If it is not the same then apologize. I have issues with the PDF rendering of a table. It seems to pick up that there needs to be a line break, but puts a bit of the new table on the previous page. See the attached example. Google Chrome 62.0.3202.94 (Official Build) (64-bit) (cohort: Stable) Revision 4fd852a98d66564c88736c017b0a0b0478e885ad-refs/branch-heads/3202@{#789} OS Windows JavaScript V8 6.2.414.42 Flash 27.0.0.187
,
Nov 27
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 28
The problem from comment #1 still exists in Chrome 72.0.3595.2.
,
Nov 28
This is probably blocked on NG?
,
Nov 28
Yes, I don't think we want to update our current table algorithm to support break-inside on table cells. Isn't this a dup of bug 601033, BTW? |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by pnangunoori@chromium.org
, Sep 11 2017Labels: Needs-Milestone OS-Mac OS-Windows
Status: Untriaged (was: Unconfirmed)
223 KB
223 KB View Download