-
Notifications
You must be signed in to change notification settings - Fork 127
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
Overflowing content of table cells get placed in the wrong column on the next page #299
Comments
Hmmm it seems it's actually not about the break tags, I get the same problem with regular content that overflows between pages:
|
Same issue here. Any word from the devs? |
+1 am having the same issue, and I can confirm that it is not specific to break tags. At least in my case, it happens whenever a row has to be split across pages. I have this problem and can reproduce the above example with 0.19 pagedown (and have also tried older versions to the same effect). |
For anybody needing a temporary hacky solution, I got it working for me by manually creating additional tables to ensure they never cross a page. |
The workaround I use is to manually add a page break at the end of the content in the last cell that fits on a page. I do this by linking a style sheet with a style like this: styles.css br.pageBreak { page-break-after: always; } Then I insert a page break by ending In |
@cderv any chance you know some magical way we might go around fixing this? :) |
No I don't have a magical way sorry. First thing would need to check somehow if the error is still present with newer version of paged.js. Unfortunately, I can't spend much time on that, but happy to review any PR is anyone found how to fix that, even a temporary workaround to add. We'll then merge and do a release with pleasure. Sorry for the inconvenience currently. |
+1, issue is still occurring. |
+1. Is there a fix? |
@cderv apologies for bumping this --- might you be able to provide some pointer about what I'd need to do check if the issue is present with the latest version of paged.js? Does Or is pagedown doing some magic with it when including, so that I'd need to somehow change the version included within pagedown? For what it's worth, this bug is actually the single stumbling block that's holding me back from using pagedown widely in my own work --- whenever I need to include tables, I know that I unfortunately can't use pagedown because it has a high likelihood of breaking. 😢 |
@ulyngs Christophe is currently on vacation. My short answer is that unfortunately, upgrading paged.js may not be straightforward. Please see #252. It seems we need to at least replace our footnote hacks #21 with paged.js's native footnote support, but I don't have much expertise on this (yet). That said, you can definitely try to upgrade paged.js and see if it just works. Actually I briefly tested the latest release of paged.js last week and ran into a bug, so I'd recommend that you try its latest beta release instead (which is currently https://unpkg.com/pagedjs@0.5.0-beta.1/dist/paged.polyfill.js). |
Just FYI, I just spent a week on writing a significantly simplified version of When an element is longer than one page, pages.js will allocate multiple pages (depending on the height of the element) for it when printing to PDF, and I rely on the web browser's built-in fragmentation capability (which is quite amazing) to break the element. Currently I've only tested it with litedown documents (which produce highly linear HTML output). In case you want to quickly test it: install.packages("litedown", repos = c("https://yihui.r-universe.dev", "https://cloud.r-project.org")) Press the Knit button in RStudio or call ---
output:
litedown::html_format:
meta:
css: ["default", "@pages"]
js: ["@pages"]
knit: litedown:::knit
---
```{r, echo=FALSE}
I(data.frame(
id = 1:100,
content = "here's a line<br>and here's another line"
))
``` Then press |
I'm running into this problem in my R Markdown template for making academic CVs with
pagedown
, and I can't figure out what's causing it or how to solve it. Here's a minimal reproducible example:Create an R Markdown file with this content:
When a page break divides up the content in second-column cells, then the remaining cell content is erroneously placed in the first column instead of in the second column:
Any idea about how to fix this?
The text was updated successfully, but these errors were encountered: