Re: [Bug report] Table splits fail due to postponed-content height constraint

Robin Becker <[email protected]> Mon, 17 Nov 2025 09:32:17 +0000
Newsgroups gmane.comp.python.reportlab.user
Message-ID <CAOBYczo4PVj9WhCcsj_ScrhP3eBrvbn+Jch3OmPM3orkcD2R6Q@mail.gmail.com>
--===============4117797878453608969==
Content-Type: multipart/alternative; boundary="0000000000009d0e2e0643c706dc"

--0000000000009d0e2e0643c706dc
Content-Type: text/plain; charset="UTF-8"

Hi Yoshua (and Christian),

1) thanks for re-raising this bug. I suspect we failed to see/use the
google list report. Google wants to control everything bah :(

2) I see a layout failure when running the example without the patch.

3) The patch fixes this particular exception.

4) I will need to run a full set of graphical comparisons to see if the fix
materially alters anything else. If OK it will go into the next release
along with the test and credits.

On Thu, 13 Nov 2025 at 21:45, Yoshua Wakeham via reportlab-users <
[email protected]> wrote:

> Hi there,
>
> I'd like to draw attention to a bug in within-row table splits.
>
> Note: this one was first reported in 2024 by Christian Zwicknagl in the
> Google mirror of this mailing list (link
> <https://groups.google.com/g/reportlab-users/c/NhklESoh3mg/m/pO8Ve7VlCgAJ>).
> It seems that the report didn't get noticed, because it was only ever
> posted to the mirror. I have adapted his test code and patch, but I don't
> have his contact details so I haven't been able to communicate with him to
> see if he would still be interested in a fix. (Christian, if you're out
> there, thank you for reporting this in 2024!)
> ...........
> Best regards,
> Yosh
>
> --
>
> *Yoshua Wakeham*...........
>
-- 
Robin Becker

--0000000000009d0e2e0643c706dc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi Yoshua (and=C2=A0Christian),</div><div><br></div><=
div>1) thanks for re-raising this bug. I suspect we failed to see/use the g=
oogle list report. Google wants to control everything bah :(</div><div><br>=
</div><div>2) I see a layout failure when running the example without the p=
atch.</div><div><br></div><div>3) The patch fixes this particular exception=
.</div><div><br></div><div>4) I will need to run a full set of graphical co=
mparisons to see if the fix materially alters anything else. If OK it will =
go into the next release along with the test and credits.</div><br><div cla=
ss=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Thu, 13 Nov 2025 at 21:45, Yoshua Wakeham via reportlab-users &lt;<a=
 href=3D"mailto:[email protected]">reportlab-users@lists=
2.reportlab.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div dir=3D"ltr"><div>Hi there,</div><div><br></div><div>I&#=
39;d like to draw attention to a bug in within-row table splits.</div><div>=
<br></div><div>Note: this one was first reported in 2024 by=C2=A0Christian =
Zwicknagl in the Google mirror of this mailing=C2=A0list (<a href=3D"https:=
//groups.google.com/g/reportlab-users/c/NhklESoh3mg/m/pO8Ve7VlCgAJ" target=
=3D"_blank">link</a>). It seems that the report didn&#39;t=C2=A0get noticed=
, because it was only ever posted to the mirror. I have adapted his test co=
de and patch, but I don&#39;t have his contact details so I haven&#39;t bee=
n able to communicate=C2=A0with him to see if he would still be interested =
in a fix. (Christian, if you&#39;re out there, thank you for reporting this=
 in 2024!)</div>...........<div>Best regards,</div><div>Yosh</div><div><div=
><br></div><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D=
"ltr" class=3D"gmail_signature"><div dir=3D"ltr"><b style=3D"color:rgb(34,3=
4,34)">Yoshua Wakeham<br></b>...........</div></div></div></div></blockquot=
e></div><span class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"lt=
r" class=3D"gmail_signature">Robin Becker<br></div></div>

--0000000000009d0e2e0643c706dc--

--===============4117797878453608969==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline