pagedjs issueshttps://gitlab.coko.foundation/pagedjs/pagedjs/-/issues2022-05-06T10:39:41Zhttps://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/332Road to Pagedjs 1.02022-05-06T10:39:41ZBoris Budiniboris@cloud68.coRoad to Pagedjs 1.0
## About tables
- splitting cells https://gitlab.pagedmedia.org/tools/pagedjs/issues/85
- check the tables files here: https://gitlab.pagedmedia.org/tools/pagedjs-table-update
- repeat colgroup / caption: https://gitlab.pagedmedia.org...
## About tables
- splitting cells https://gitlab.pagedmedia.org/tools/pagedjs/issues/85
- check the tables files here: https://gitlab.pagedmedia.org/tools/pagedjs-table-update
- repeat colgroup / caption: https://gitlab.pagedmedia.org/tools/pagedjs/issues/238
- repeat table header https://gitlab.pagedmedia.org/tools/pagedjs/issues/84
- empty row when the break token is inside an element inside a cell: https://gitlab.pagedmedia.org/tools/pagedjs/issues/240
- css counters in tables: https://gitlab.pagedmedia.org/tools/pagedjs/issues/225
- a splitted table that don’t respect page margin: https://gitlab.pagedmedia.org/tools/pagedjs/issues/209
- `break-after: avoid` doesnt work on thead element: https://gitlab.pagedmedia.org/tools/pagedjs/issues/135
- Preview crashes with TypeError: undefined is not iterable in Layout.findOverflow: #331
- Table break when cut in inline element: #360
- Tables ok on screen, not good on print #344
seems fixed / can’t replicate:
- lost cells when split https://gitlab.pagedmedia.org/tools/pagedjs/issues/227
## About flex and grid
- Using flex and grid break the rendering as it finds an overflow as soon as the first column hit the bottom of the page. We need to stop the overflowing if the latest element is either flex or grid, and move the breakToken accordingly (see: https://gitlab.pagedmedia.org/tools/pagedjs/-/issues/276 or https://gitlab.pagedmedia.org/tools/pagedjs/-/issues/242 and https://gitlab.pagedmedia.org/tools/pagedjs/-/issues/328)
## web component elements
Web component doesn’t show correctly: https://gitlab.pagedmedia.org/tools/pagedjs/-/issues/231 and https://gitlab.pagedmedia.org/tools/pagedjs/-/issues/148
On the same note, tables in custom-elements: https://gitlab.pagedmedia.org/tools/pagedjs/issues/289https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/168Dynamic content preview2022-03-21T17:08:55ZBoris Budiniboris@cloud68.coDynamic content previewRendering multiple hundereds of pages is super slow and needs a lot of network data. Therefore I want to be able to only render some pages, and dynamically add pages before or after (whatever is needed) the current rendererd preview.
T...Rendering multiple hundereds of pages is super slow and needs a lot of network data. Therefore I want to be able to only render some pages, and dynamically add pages before or after (whatever is needed) the current rendererd preview.
The interface could look like:
```javascript
const paged = new Previewer();
paged.preview(content, ['/preview.css'], target) // first render
paged.previewAppend(contentAfter)
paged.previewPrepend(contentBefore)
```
Some side effects:
- Page number: If I want to render content in the middle of the book, the page numbers may not work anymore, as I don't know on which page I am. A first implementation could either
- sacrifice the page number at all
- the first page number needs to be set via an argument
- only allow to render the first few pages and then dynamically `append` contenthttps://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/410Counter reset footnote, page, etc. breaks everything2023-10-05T14:19:58Zjulientaqjulien@coko.foundationCounter reset footnote, page, etc. breaks everythingIn the counter reset specs file, we can see that, to reset the footnote number, you need to reset the page number like this:
`counter-reset: page 1 footnote;`
but most of the user will not have that information, as they would assume t...In the counter reset specs file, we can see that, to reset the footnote number, you need to reset the page number like this:
`counter-reset: page 1 footnote;`
but most of the user will not have that information, as they would assume that the counter-reset should only touch what we reset, *ie* `counter-reset: footnote 1`.
What options do we have to have working multiple page reset?https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/400TypeScript?2023-01-17T11:14:10ZMatias SalgadoTypeScript?Would be nice to add TypeScript support for those codebases.Would be nice to add TypeScript support for those codebases.https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/276Paged.js pushes columns onto the next page when parsing a flexbox based grid ...2021-12-14T21:56:06ZBoris Budiniboris@cloud68.coPaged.js pushes columns onto the next page when parsing a flexbox based grid systemMy use case involves the Salesforce grid (SLDS Grid: https://www.lightningdesignsystem.com/utilities/grid/). You can download SLDS CSS system here: https://www.lightningdesignsystem.com/resources/downloads/
However, any other grid syste...My use case involves the Salesforce grid (SLDS Grid: https://www.lightningdesignsystem.com/utilities/grid/). You can download SLDS CSS system here: https://www.lightningdesignsystem.com/resources/downloads/
However, any other grid system built on flexbox would have the same issue. Here is a simple example using http://flexboxgrid.com/:
[flexbox_example.html](/uploads/00f30962432c5dfc40bc07a184b668b7/flexbox_example.html)
**Before Paged.js processing:**
![Screen_Shot_2021-02-18_at_2.44.11_PM](/uploads/7e19cf79db771c090706d362d33a35f9/Screen_Shot_2021-02-18_at_2.44.11_PM.png)
**After Paged.js processing (print modal):**
![Screen_Shot_2021-02-18_at_2.44.59_PM](/uploads/9f2b2628a06b2c9f186665dbf9e3d7f7/Screen_Shot_2021-02-18_at_2.44.59_PM.png)
![Screen_Shot_2021-02-18_at_2.45.08_PM](/uploads/cec757189bb0fff48152c15cba0bbe98/Screen_Shot_2021-02-18_at_2.45.08_PM.png)
![Screen_Shot_2021-02-18_at_2.45.19_PM](/uploads/ba6b6e56e4c5213e5d4814c48fd2a61b/Screen_Shot_2021-02-18_at_2.45.19_PM.png)
![Screen_Shot_2021-02-18_at_2.45.25_PM](/uploads/344d8c722ed6f0eeaa63d835593063f8/Screen_Shot_2021-02-18_at_2.45.25_PM.png)
At a higher level, the issue is more about 'side-by-side' content and multiple overflow points. Floats (left/right), use of display: grid, etc would have similar behavior. Whether they can be solved in the same manner is another question.https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/246Table overflow premature breaks2020-09-12T11:37:31ZBoris Budiniboris@cloud68.coTable overflow premature breaksI have a table that spans about 25 pages or so, about 5 columns and each td has an arbitrary length of text that may or may not wrap to multiple lines. The problem with this is as soon as a few td's have their text wrapped to a new line ...I have a table that spans about 25 pages or so, about 5 columns and each td has an arbitrary length of text that may or may not wrap to multiple lines. The problem with this is as soon as a few td's have their text wrapped to a new line and this goes on for multiple elements across the whole documents, you start seeing weird behavior of random breaks in the table. Neither orphans or break-inside can prevent this.
![image](/uploads/070e01b16f54b058c2e22963d4a4a41f/image.png)
Only thing that does prevent this without modifying any content is to set all tables to `height: 100%` but then when I actually want a break before something that last table will just look weird. And to prevent this while modifying your content is to prevent word wraps which is also counter intuitive.https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/242display: flex pushes the next columns on the next page2021-12-14T21:56:06ZBoris Budiniboris@cloud68.codisplay: flex pushes the next columns on the next pageConsider the following example: [flex-columns.html](/uploads/5c9a39041e9ce4a37787ff9bba29d9a5/flex-columns.html)
And here's the result without Paged.js:
![without-pagedjs1](/uploads/76fa46e2e6e4abfd114141e97ff24e03/without-pagedjs1.png...Consider the following example: [flex-columns.html](/uploads/5c9a39041e9ce4a37787ff9bba29d9a5/flex-columns.html)
And here's the result without Paged.js:
![without-pagedjs1](/uploads/76fa46e2e6e4abfd114141e97ff24e03/without-pagedjs1.png)
And the result with Paged.js:
![with-pagedjs1](/uploads/db576e20d5635a9ed7af2aecb3417b14/with-pagedjs1.png)
Since I'm familiar with the codebase it makes sense but I think this is not the expected result, right?
I think the result should be:
![with-pagedjs-expected](/uploads/1a2c44d3eddaac52e6ceb257dd94cd31/with-pagedjs-expected.png)https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/227Some cells are lost when a table is chunked2022-02-03T23:01:49ZBoris Budiniboris@cloud68.coSome cells are lost when a table is chunkedHere's a mostly unstyled document that contains a table with a big cell: [long-table.html](/uploads/a84c4a1452a3f9d8780e53efec008fc5/long-table.html).
As you can see the the author cell on the first page is missing and on the second pag...Here's a mostly unstyled document that contains a table with a big cell: [long-table.html](/uploads/a84c4a1452a3f9d8780e53efec008fc5/long-table.html).
As you can see the the author cell on the first page is missing and on the second page, the table only contains two columns (the issue and date columns are missing).https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/222CSS grid elements doesn’t work correctly on multiple pages2020-06-27T11:42:01ZBoris Budiniboris@cloud68.coCSS grid elements doesn’t work correctly on multiple pagesIf an element display in CSS grid overflows on multiple page, children are not broken correctly.
With a simple grid in two columns, the expected behavior is the following (as if we cut the element and is children (A & B) to make several...If an element display in CSS grid overflows on multiple page, children are not broken correctly.
With a simple grid in two columns, the expected behavior is the following (as if we cut the element and is children (A & B) to make several pages)
![schema-grid_expected](/uploads/7add2fc51e647bd72848028bcbd65825/schema-grid_expected.png)
The result in paged.js is as follow:
![schema-grid_result](/uploads/325474510de25c50666caf69abe58ca8/schema-grid_result.png)
It seems that it is the first child (A) which is first rendered in the grid and then when iy has finished rendering, the second child (B) finally appears on the page. I think it's because Paged.js reads the DOM elements one by one to render them but doesn't take into account that the parent is displayed in CSS grid.
HTML example: [issue-grid.html](/uploads/f692dcbdf019a5e97403899793390d9d/issue-grid.html)https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/171leader() support2024-03-14T04:42:11ZBoris Budiniboris@cloud68.coleader() supportThis binds a headline and its page number within a Table of Content.
Specification is here: https://www.w3.org/TR/css-gcpm-3/#leaders
Expected output:
```
Table of Contents
1. Loomings.....................1
2. The Carpet-Bag.............This binds a headline and its page number within a Table of Content.
Specification is here: https://www.w3.org/TR/css-gcpm-3/#leaders
Expected output:
```
Table of Contents
1. Loomings.....................1
2. The Carpet-Bag...............9
3. The Spouter-Inn.............13
```
Related issue: https://github.com/Mogztter/asciidoctor-pdf.js/issues/126https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/94Merge @page rules from different CSS sources2023-05-04T14:19:20ZBoris Budiniboris@cloud68.coMerge @page rules from different CSS sourcesHaving two `@page` rules in the same CSS file, or in the same `<style>` element works as expected.
But if you have two non-empty `@page` rules in two separate elements (or files), the cascade doesn't work.
Minimal repro:
```html
<!DOC...Having two `@page` rules in the same CSS file, or in the same `<style>` element works as expected.
But if you have two non-empty `@page` rules in two separate elements (or files), the cascade doesn't work.
Minimal repro:
```html
<!DOCTYPE html>
<html>
<head>
<style>
@page {
size: A4;
}
</style>
<style>
@page {
margin-top: 6cm;
}
</style>
</head>
<body>
<h1>foo</h1>
<script src="https://unpkg.com/pagedjs/dist/paged.polyfill.js"></script>
</body>
</html>
```
- Expected: the `margin-top` pushes down the `foo` header in the layout.
- Actual: the `margin-top` is ignored.
Thanks for looking into this! I'm happy to help in any way I can. But looking at the code, I'm uncertain about some of the reasoning that went into it. And I don't want to invest a lot of time in a pull request if you prefer to fix it yourself / your way...https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/370Ordered list numbering is lost near page break2022-10-17T13:53:02ZGuillaume GrossetieOrdered list numbering is lost near page breakConsider the following example (you might need to tweak the page margin to break just after a list item):
```html
<!DOCTYPE html PUBLIC>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<meta...Consider the following example (you might need to tweak the page margin to break just after a list item):
```html
<!DOCTYPE html PUBLIC>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
<meta http-equiv="Content-Style-Type" content="text/css"/>
<title>Issue #370</title>
<script src="https://unpkg.com/pagedjs/dist/paged.polyfill.js"></script>
<style>
:root {
font-size: 18px;
}
/* interface */
@media screen {
body {
background: whitesmoke;
}
.pagedjs_page {
background: white;
margin-bottom: 10px;
box-shadow: 0 0 0 1px rgba(0, 0, 0, 0.2);
}
.pagedjs_pages {
width: calc(var(--pagedjs-width) * 2);
display: flex;
flex-direction: row;
flex-wrap: wrap;
justify-content: flex-start;
margin: 0 auto;
}
}
@page {
size: A4;
margin: 2mm 0;
}
</style>
</head>
<body>
<section class="chapter">
<div id="content" class="content">
<div class="qlist qanda">
<ol>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
<li>
<p><em>This is a question?</em></p>
<p>This is an answer.</p>
</li>
</ol>
</div>
</div>
</section>
</body>
</html>
```
You will get the following result:
![image](/uploads/cb055c62a98ab8244f8741232675d6bd/image.png)
As you can see, the number 15 is missing.
I can reproduce this issue on the main branch.https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/363`<br>` breaks rendering2023-01-17T18:49:16Zjulientaqjulien@coko.foundation`<br>` breaks renderingJust `<br>` between pages and an infinite loop appears [test_pagedjs.html](/uploads/07be499f7f60f54ef2b457c1cd2dc573/test_pagedjs.html)
*By Shut on 2021-09-23T23:49:32 (imported from GitLab)*Just `<br>` between pages and an infinite loop appears [test_pagedjs.html](/uploads/07be499f7f60f54ef2b457c1cd2dc573/test_pagedjs.html)
*By Shut on 2021-09-23T23:49:32 (imported from GitLab)*https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/328Layout with two columns is not displaying properly2023-11-03T11:30:57ZBoris Budiniboris@cloud68.coLayout with two columns is not displaying properlyHello there,
I have a problem with my rendered page. It contains 2 columns and html look like that:
```
<div class="page_layout">
<div class="sidebar"></div>
<div class="main-content"></div>
</div>
```
Everything works fine if ma...Hello there,
I have a problem with my rendered page. It contains 2 columns and html look like that:
```
<div class="page_layout">
<div class="sidebar"></div>
<div class="main-content"></div>
</div>
```
Everything works fine if main-content has more text than sidebar but if sidebar have more content and need to be moved to next page my main-content div shifts to next page or even to next page if sidebar takes place of 2 pages. I created image how it look like:
![what-is](/uploads/8ae4945d6ed6785ec7335f230a8ad706/what-is.png)
I tried using display grid on .page_layout, display:flex and event adding each column position:absolute with proper width and nothng helped.
Tried to add more content to sidebar and no matter how much content is in sidebar main-content will start at the end of sidebar height.
Any ideas how to fix it?https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/297When pages have different sizes, the resulting PDF has all pages the same2021-05-05T22:39:47ZBoris Budiniboris@cloud68.coWhen pages have different sizes, the resulting PDF has all pages the sameThere are legitimate reasons to have pages with various sizes, for example when one has a printer which supports many paper sizes, or when only printing to PDF. That can be achieved using something like this:
```css
@page {
size: A4 ...There are legitimate reasons to have pages with various sizes, for example when one has a printer which supports many paper sizes, or when only printing to PDF. That can be achieved using something like this:
```css
@page {
size: A4 landscape;
}
@page:left {
size: A5 landscape;
background-color: blue;
}
@page:right {
background-color: red;
}
```
When one tries this in a (non-polyfilled) Chromium 90, the page sizes in the resulting PDF are correct, but the page layout is computed incorrectly which causes the text to overflow ([bug 835358](https://bugs.chromium.org/p/chromium/issues/detail?id=835358)).
![image](/uploads/8662afaaa570b81335e863bc22653b16/image.png)
Trying again with a PagedJS Polyfill v0.1.43, the layout is computed correctly this time (even rendering the colors this time), but the actual size of the page stays the same.
![image](/uploads/582c52ee884c6c855365e4dcc83257d6/image.png)
This is because the `width` and `height` of a `.pagedjs_page` are set to `--pagedjs-width-left`, however only `--pagedjs-pagebox-width` is updated for the page. The computed styles are:
```css
:root {
--pagedjs-orientation: landscape;
--pagedjs-width: 297mm;
--pagedjs-height: 210mm;
--pagedjs-width-right: 297mm;
--pagedjs-height-right: 210mm;
--pagedjs-width-left: 297mm;
--pagedjs-height-left: 210mm;
}
.pagedjs_page {
--pagedjs-pagebox-width: 297mm;
--pagedjs-pagebox-height: 210mm;
}
.pagedjs_page.pagedjs_left_page {
--pagedjs-pagebox-width: 210mm;
--pagedjs-pagebox-height: 148mm;
}
.pagedjs_page.pagedjs_left_page {
width: var(--pagedjs-width-left); /* results to 297mm, not 210mm */
height: var(--pagedjs-height-left); /* results to 210mm, not 148mm */
}
```
Would it be possible to fix this behavior and make the pages correctly sized?https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/245"break-inside: avoid" rule should be ignored when the element cannot fit on t...2020-09-11T11:56:14ZBoris Budiniboris@cloud68.co"break-inside: avoid" rule should be ignored when the element cannot fit on the next pageCurrently, Paged.js will move the element to the next page:
![localhost_63342_pagedjs_specs_breaks_break-inside_break-inside-avoid_long-section.html__ijt_ouvrkki9j4o2r0e60h0p1l9is3_Laptop_with_MDPI_screen_](/uploads/3bd7d74862f26620f79e...Currently, Paged.js will move the element to the next page:
![localhost_63342_pagedjs_specs_breaks_break-inside_break-inside-avoid_long-section.html__ijt_ouvrkki9j4o2r0e60h0p1l9is3_Laptop_with_MDPI_screen_](/uploads/3bd7d74862f26620f79e032bd7824218/localhost_63342_pagedjs_specs_breaks_break-inside_break-inside-avoid_long-section.html__ijt_ouvrkki9j4o2r0e60h0p1l9is3_Laptop_with_MDPI_screen_.png)
And then, since the element still does not fit on the page, Paged.js will rightfully break the element and thus, ignore the impractical rule (i.e. impossible to comply).
In the end, Paged.js adds unnecessary blank space. It would be better to ignore the rule right away and produces:
![localhost_63342_pagedjs_specs_breaks_break-inside_break-inside-avoid_long-section.html__ijt_dp8clis2stupeer3p5pjpf3f8u_Laptop_with_MDPI_screen_](/uploads/f5cc86901195b8160e99a385834f52a0/localhost_63342_pagedjs_specs_breaks_break-inside_break-inside-avoid_long-section.html__ijt_dp8clis2stupeer3p5pjpf3f8u_Laptop_with_MDPI_screen_.png)https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/143target-counter when url isn't found2022-03-21T16:47:59ZBoris Budiniboris@cloud68.cotarget-counter when url isn't foundCurrently, target-counter emits `0` as the page number if a given url isn't found. Conditional on support by the spec, it would seem more correct that no page number should be emitted when a page wasn't found.Currently, target-counter emits `0` as the page number if a given url isn't found. Conditional on support by the spec, it would seem more correct that no page number should be emitted when a page wasn't found.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/80Rendering in loop (new duplicated content behaviour)2022-03-21T10:14:22ZBoris Budiniboris@cloud68.coRendering in loop (new duplicated content behaviour)Rendering is in loop while trying to render this article.
Content is being duplicated forever....
[sample.zip](/uploads/ea8ba3032236050e1cb2f9b1ca0af6d5/sample.zip)Rendering is in loop while trying to render this article.
Content is being duplicated forever....
[sample.zip](/uploads/ea8ba3032236050e1cb2f9b1ca0af6d5/sample.zip)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 :)