pagedjs issueshttps://gitlab.coko.foundation/pagedjs/pagedjs/-/issues2022-06-21T21:36:37Zhttps://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/360Unable to Layout Item within Table2022-06-21T21:36:37Zm oUnable to Layout Item within TableHi,
when a table cell is breaking and the cut is within a strong tag (or another one) I receive the error _Unable to Layout Item within Table_.
The result is that it stops rendering the following pages and therefore content is missing.
...Hi,
when a table cell is breaking and the cut is within a strong tag (or another one) I receive the error _Unable to Layout Item within Table_.
The result is that it stops rendering the following pages and therefore content is missing.
When no tag is used, all is fine.
It can be reproduced with Chrome (97):
[index.html](/uploads/0915ee65a0ece623f55c3b2ce02391c0/index.html).https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/357Overflowing content in Windows2022-04-07T00:22:44ZHarshna HaswaniOverflowing content in WindowsWhen I rendered a file with PagedJS, I noticed that paragraphs were missing. This was tracked using IDs assigned to paragraphs. On inspecting, it was found that the paragraphs were rendered but the overflow was not managed. I use a Windo...When I rendered a file with PagedJS, I noticed that paragraphs were missing. This was tracked using IDs assigned to paragraphs. On inspecting, it was found that the paragraphs were rendered but the overflow was not managed. I use a Windows system. When the same file was rendered on a Mac device, there was no problem. On Windows, I tested it across multiple browsers - Edge, Chrome, and Brave. Earlier, I also came across this issue with missing images when I was using hooks.
Note: If it works properly on first test, go back and reopen the file. Below, I have attached a few images for reference
![Image_Pasted_at_2022-1-19_17-31](/uploads/dc62f35e99f0e3c0901db966ea8a8798/Image_Pasted_at_2022-1-19_17-31.png)
![Image_Pasted_at_2022-1-19_17-32](/uploads/ce4b061312cd47bc2ed2d3ade0050684/Image_Pasted_at_2022-1-19_17-32.png)
![Screenshot_2022-01-20_184629](/uploads/1e053947a5e2d2291333e4ef9cb6852f/Screenshot_2022-01-20_184629.png)
![Screenshot_2022-01-20_184534](/uploads/ac42f788cbb3aa2239e167af4ee48095/Screenshot_2022-01-20_184534.png)
![Screenshot_2022-01-20_184439](/uploads/7cf512330f82c2bdbfadf2a9216b205c/Screenshot_2022-01-20_184439.png)Fred ChasenFred Chasenhttps://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/344Tables are fine on screen, but missing row on print2022-12-23T23:16:00ZBoris Budiniboris@cloud68.coTables are fine on screen, but missing row on printBefore everything, great work.
We have pretty big tables in our documents and we managed to show them right on screen, but when we try to print them, after second page table's row missing at the beginning of every page.[PPP-v5-sample.ht...Before everything, great work.
We have pretty big tables in our documents and we managed to show them right on screen, but when we try to print them, after second page table's row missing at the beginning of every page.[PPP-v5-sample.html](/uploads/9e1da2018bfb32ad0886c29bd3d4d15b/PPP-v5-sample.html)
Please advice us that is the root cause, and how to fix this issue.
vbr,https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/135Cannot surpress line break after `thead`2022-03-21T16:58:23ZBoris Budiniboris@cloud68.coCannot surpress line break after `thead`Example HTML:
```html
<html>
<head></head>
<style>
@media print {
@page {
size: A4;
}
thead {
break-after: avoid;
}
}
</style>
</head>
<body>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>...Example HTML:
```html
<html>
<head></head>
<style>
@media print {
@page {
size: A4;
}
thead {
break-after: avoid;
}
}
</style>
</head>
<body>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<p>foo</p>
<table>
<thead>
<tr>
<th>a</th>
<th>b</th>
<th>c</th>
</tr>
</thead>
<tbody>
<tr>
<td><p>a</p></td>
<td><p>b</p></td>
<td><p>c</p></td>
</tr>
<tr>
<td><p>a</p></td>
<td><p>b</p></td>
<td><p>c</p></td>
</tr>
</tbody>
</table>
</div>
</body>
</html>
```
Rendered to pdf using the pagedjs-cli.https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/133Repeating table headers or recursive pagination2022-05-29T07:58:09ZBoris Budiniboris@cloud68.coRepeating table headers or recursive paginationI often have situations where I want to display tabular data which doesn't fit on one page. It would be good for readability if the table header could be repeated on each new page.
I'm starting this discussion because I'd like some inpu...I often have situations where I want to display tabular data which doesn't fit on one page. It would be good for readability if the table header could be repeated on each new page.
I'm starting this discussion because I'd like some input on how to achieve this, maybe I am ignoring something obvious from the polyfill or paged media standard. Mostly I am talking about automatically generated content which means I would like to avoid manual tweaks for individual cases.
The only thing I can see is to create a new page class with the table header as background or generated content. But that limits what I can do with the header, the table has to start at the top of a page instead of flowing after other content, and also I think there can't be other content after the table on the same page if space is left. The latter may be achieved through attaching a page class to the trailing content and hope it is overwritten by the table's page class if both appear on the same page. Getting all of this done with regular HTML table markup and generic enough for dynamically generated content and dynamically sized rows is even trickier.
The other way to think about this problem is something like recursive pagination: The table is represented as a box, and if that box has to be split among multiple pages, it would need to be able to generate additional content which isn't bound to the page but rather to the sub-page. Ideally it could have a table header at the start of the table flowing after other content, and maybe even a footer element at the final end of the table followed by other content. Ideally it would also be able to finetune the pagination (orphans, widows, page-break-before/inside/after etc).
A similar use case would be where there are two or more independent flows of content on the same sequence of pages. Like a set of pictures with one on each top of a page and a story text on the bottom. This could also be achieved through defining different page types, but it would be very verbose and not very generic.
Yet another idea is to use the CSS Houdini Layout API, but I haven't looked into that enough, yet.
I welcome any suggestions on how to do things like that,
And thank you all for your great work on paged media!https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/114CSS break-after directive does not work properly2022-03-21T15:06:38ZBoris Budiniboris@cloud68.coCSS break-after directive does not work properlyHi,
The directive for defining page breaks does not always work as expected.
We want to display a table and we want to prevent having an orphan table head at the end of a page.
To prevent this we have configured the following directiv...Hi,
The directive for defining page breaks does not always work as expected.
We want to display a table and we want to prevent having an orphan table head at the end of a page.
To prevent this we have configured the following directive:
```
thead {
break-inside: avoid;
break-after: avoid;
}
```
It works in some cases, but in this specific case it does not work (Chrome):
![image](/uploads/ff1efd86230a4a3299d4434b9ac62cf2/image.png)
If we look carefully the screenshot, the thead element is not the last element on the page. This is probably why the directive is not applied accordingly. The last element of the page is a tbody. Having a tbody (height equals to 0) without any child elements does not make sense in our case.
How can I avoid such behaviour? Do you have any example how to adjust the break element through a custom PageHandler?
Any help would be greatly appreciated,
Alexandrehttps://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/85Broken cell on multipage table2022-06-14T18:18:22ZBoris Budiniboris@cloud68.coBroken cell on multipage tableI have a table that spread across multiple pages and one cell is "broken":
![cell-break](/uploads/b8fbb41f9bdf3faf1dd528ae2813f7a4/cell-break.png)
As you can see "Native support" should be on the row "Document header" and "/docs/writin...I have a table that spread across multiple pages and one cell is "broken":
![cell-break](/uploads/b8fbb41f9bdf3faf1dd528ae2813f7a4/cell-break.png)
As you can see "Native support" should be on the row "Document header" and "/docs/writing-posts" should be on the cell "Slapped on as front matter".
If I change my viewport (ie. resize my browser window) then I get a different result:
![empty-cell](/uploads/3c5668b8cbbeb9c20ffb1002a8df1a94/empty-cell.png)
Notice the empty cell below "Typographic".
I've attached my HTML5 document with my two stylesheets.
[document_test.html](/uploads/db60581702d4e21b49c0abaff6fa9e30/document_test.html)
[document.css](/uploads/39ca5d80977c030fadcc5fc5d95b5ef6/document.css)
[asciidoctor.css](/uploads/6f35dea9213b588621f8344afd196e2f/asciidoctor.css)https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/84Repeat table header on subsequent pages2022-11-29T18:20:40ZBoris Budiniboris@cloud68.coRepeat table header on subsequent pagesI have a long `<table>` that spread across two or more pages.
If I print this HTML page with Chrome (without Paged.js) then the header is repeated on subsequent pages:
![header](/uploads/5e572b8ec65f384592ebd6afc97c0a1e/header.png)
Thi...I have a long `<table>` that spread across two or more pages.
If I print this HTML page with Chrome (without Paged.js) then the header is repeated on subsequent pages:
![header](/uploads/5e572b8ec65f384592ebd6afc97c0a1e/header.png)
This feature is pretty useful and I was wondering if it's currently possible to do the same with Paged.js ? If not, would you consider adding this feature (as the default behavior or behind a configuration flag) ?
Thanks :)