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

Yoshua Wakeham via reportlab-users <[email protected]> Mon, 17 Nov 2025 10:18:03 -0500
Newsgroups gmane.comp.python.reportlab.user
Message-ID <CAPt=5qTMEBnHxAYrLS1xY18Od2=HEp2yte=uc7cqMCoxqhsuMQ@mail.gmail.com>
--===============5908627688373921336==
Content-Type: multipart/alternative; boundary="0000000000002b921f0643cbdb84"

--0000000000002b921f0643cbdb84
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks Robin! I look forward to hearing from you.

Also for the record, the Google mirror doesn't actually seem to be
mirroring the mailing list any more =E2=80=93 looking over the mailing list=
 archive
for the past few months, none of those threads are in the Google group.

Yosh

On Mon, Nov 17, 2025 at 4:32=E2=80=AFAM Robin Becker <[email protected]> =
wrote:

> 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 relea=
se
> 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/pO8Ve7VlCgA=
J>).
>> 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
>

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

<div dir=3D"ltr">Thanks Robin! I look forward to hearing from you.<div><br>=
</div><div>Also for the record, the Google mirror doesn&#39;t actually seem=
 to be mirroring the mailing list any more =E2=80=93 looking over the maili=
ng list archive for the past few months, none of those threads are in the G=
oogle group.</div><div><br></div><div>Yosh</div></div><br><div class=3D"gma=
il_quote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Mo=
n, Nov 17, 2025 at 4:32=E2=80=AFAM Robin Becker &lt;<a href=3D"mailto:robin=
@reportlab.com">[email protected]</a>&gt; wrote:<br></div><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><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 google list report. Google wants to cont=
rol everything bah :(</div><div><br></div><div>2) I see a layout failure wh=
en running the example without the patch.</div><div><br></div><div>3) The p=
atch fixes this particular exception.</div><div><br></div><div>4) I will ne=
ed 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.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Thu, 13 Nov 2025 at 21:45, Yoshua Wakeham via reportla=
b-users &lt;<a href=3D"mailto:[email protected]" target=
=3D"_blank">[email protected]</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Hi th=
ere,</div><div><br></div><div>I&#39;d like to draw attention to a bug in wi=
thin-row table splits.</div><div><br></div><div>Note: this one was first re=
ported in 2024 by=C2=A0Christian Zwicknagl in the Google mirror of this mai=
ling=C2=A0list (<a href=3D"https://groups.google.com/g/reportlab-users/c/Nh=
klESoh3mg/m/pO8Ve7VlCgAJ" target=3D"_blank">link</a>). It seems that the re=
port didn&#39;t=C2=A0get noticed, because it was only ever posted to the mi=
rror. I have adapted his test code and patch, but I don&#39;t have his cont=
act details so I haven&#39;t been able to communicate=C2=A0with him to see =
if he would still be interested in a fix. (Christian, if you&#39;re out the=
re, thank you for reporting this in 2024!)</div>...........<div>Best regard=
s,</div><div>Yosh</div><div><div><br></div><span class=3D"gmail_signature_p=
refix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D=
"ltr"><b style=3D"color:rgb(34,34,34)">Yoshua Wakeham<br></b>...........</d=
iv></div></div></div></blockquote></div><span class=3D"gmail_signature_pref=
ix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">Robin Becker<b=
r></div></div>
</blockquote></div>

--0000000000002b921f0643cbdb84--

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