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
I'm expecting that the second <ul> will be on the next page. Also note that some_class is a div with a background-image that fills a single page. I'm thinking that it's the one causing the issue. Is there a workaround for this?
The text was updated successfully, but these errors were encountered:
I'm expecting that the second <ul> will be on the next page.
Your CSS asks for a page break after the second ul, not before. If you want to put your second ul on the second page, you want to add a page break before it, so you have to use break-before instead of break-after.
(There’s also a problem in the way your ul tags are nested: you can’t put a ul directly in a ul, you have to put them in a li tag:
Hi @liz, thanks for the swift response. With regards to this
Your CSS asks for a page break after the second ul, not before. If you want to put your second ul on the second page, you want to add a page break before it, so you have to use break-before instead of break-after.
This was just an honest mistake because I tried simplifying the issue here, I meant for it to be break-before for this issue. In the original code it's break-after because there are more elements. I wanted that for each page it would break for every nth element.
I was able to get this to work by setting the background image height to auto and using position relative instead of absolute.
I currently have an issue with
weasyprint
version 62.3 where I can't force a page-break on the second<ul>
if it's nested inside a<div>
Given this simple layout
My css looks like this
I'm expecting that the second
<ul>
will be on the next page. Also note thatsome_class
is a div with a background-image that fills a single page. I'm thinking that it's the one causing the issue. Is there a workaround for this?The text was updated successfully, but these errors were encountered: