Guillaume Ayoub

Hi! Did you try to set a width, and negative margins on left and right sides of the image? That’s a common way to get CSS boxes bleeding over page...

Hi! Thanks for the bug report. Python 3.14b2 no-GIL, that’s living on the bleeding edge! The stack trace you reported only mentions Python and [cffi](https://github.com/python-cffi/cffi), so I suppose the bug...

I don’t have the problem anymore with 3.14.0b4. Feel free to add a comment if there’s anything more we can do on this topic!

Thanks a lot for the report. The problem is known for flex, it’s now referenced in #2400. Let’s keep this issue for this topic. The equivalent problem for grid is...

> * the first two tables are not properly aligned (see antennahouse.pdf as reference) That’s because of the 8px margin set in the user agent stylesheet (in WeasyPrint, probably in...

Hi! > Will WeasyPrint support the new spec for the 'background-clip' property in the future? That would be a good idea! This value has been added in [Background Level 4](https://drafts.csswg.org/css-backgrounds-4/#background-clip),...

Hi! That’s because `col-*-*` elements have `position: relative` set. According to the [specification](https://drafts.csswg.org/css-break/#break-between), `break-after` can `break-before` can only be set on "boxes in the normal flow of the fragmentation root",...

Well, it may be more complicated than that, `relative` is not `absolute` or `fixed`, and relative elements are actually in the flow.

It’s actually because it’s `float: left`, and we don’t break on floating elements. We should though: "User agents should also apply these properties to floated boxes whose containing block is...

Short sample to reproduce the problem: ```html float end ```