-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
page property can give rise to empty sections #145
Comments
Do you mean that if you omit display:none, then there will be a blank page before the bodymatter? This sounds like the right behavior to me. In that case the empty page shows that there is a frontmatter, but it is empty. Suppressing that empty page is an 'optimization'. |
A blank sheet, yes.
Yes. I know, that needs fixing too. It's a different issue though. |
Yes, just trying to get the requirements/terminology clear. :) |
K, thnx ;) |
Note that since commit 16a4e34, empty sections can not be caused by |
page
property can give rise to empty sections
Needs test to check whether this is still an issue. |
Back in commit 8d1a23a I removed a step from
css-to-obfl
that deleted empty sections, and instead tried to make sure that no empty sections where created in the first place, by properly propagating page breaks before runningcss:split
. This seemed like a much better approach because it follows the CSS model better, and also because the step that was responsible for deleting empty sections was doing something that I much rather wanted to leave up to the actual formatter (Dotify).The downside of this change is that a
page
property can give rise to empty section in some cases, possibly because the propagating of page breaks is possibly not done correctly, but that is hard to say because the CSS specification isn't entirely clear on this. This is an example where the frontmatter will be in an empty section because the forced page break beforebodymatter
is not propagated:My reasoning was that this should be fixed by setting
frontmatter
todisplay: none
so I left the behavior as it is. One thing that I didn't think of is that it is not always straightforward (but not impossible) to tell whenfrontmatter
will be empty because theflow
property can be used to move certain descendants out.The text was updated successfully, but these errors were encountered: