You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The below code snippet shows a minimal use case where I would expect the text 'This test has passed.' to show on the page. Using WeasyPrint v63.1, the text is not visible, but can be selected/copied when highlighting the page (i.e. it is being rendered).
When generating a PDF, it seems absolute children of relative parents that are using overflow: hidden aren't displayed at all. This issue looks similar to #996 but no flex boxes are used.
This seems to happen for all inline elements (<strong>, <span>, <em>, <abbr> tested) and other elements using display: inline (<div> tested). It displays correctly in my usual browser (Safari v18.2, including in print mode), and on this CodePen.
I'd be keen to have a crack at fixing it, but I'd be lost on where to start in the codebase or at what could be causing it.
Any tips would be awesome.
<html><head><style>
#parent {
position: relative;
overflow: hidden;
}
#child {
position: absolute;
}
</style></head><body><spanid="parent"><spanid="child">
This test has passed.
</span></span></body></html>
Hi team,
The below code snippet shows a minimal use case where I would expect the text 'This test has passed.' to show on the page. Using WeasyPrint v63.1, the text is not visible, but can be selected/copied when highlighting the page (i.e. it is being rendered).
When generating a PDF, it seems absolute children of relative parents that are using
overflow: hidden
aren't displayed at all. This issue looks similar to #996 but no flex boxes are used.This seems to happen for all inline elements (
<strong>
,<span>
,<em>
,<abbr>
tested) and other elements usingdisplay: inline
(<div>
tested). It displays correctly in my usual browser (Safari v18.2, including in print mode), and on this CodePen.I'd be keen to have a crack at fixing it, but I'd be lost on where to start in the codebase or at what could be causing it.
Any tips would be awesome.
Resulting PDF:
bug.pdf
The text was updated successfully, but these errors were encountered: