pagedjs issueshttps://gitlab.coko.foundation/pagedjs/pagedjs/-/issues2023-09-26T20:29:29Zhttps://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/148Web components and paged.js2023-09-26T20:29:29ZBoris Budiniboris@cloud68.coWeb components and paged.jsThis is an error showing how web components are handled with paged.js.
![image](/uploads/c5437aad15fd2d281a4931757f55a582/image.png)
The shadow DOM elements produced by the component are not direct children of the element, and therefor...This is an error showing how web components are handled with paged.js.
![image](/uploads/c5437aad15fd2d281a4931757f55a582/image.png)
The shadow DOM elements produced by the component are not direct children of the element, and therefore breaks the rendering.
[Archive.zip](/uploads/f1f8aa94ca082f639f75c1381c2b98b4/Archive.zip)https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/120Paged.js polyfill breaks Polymer elements2023-05-04T14:19:55ZBoris Budiniboris@cloud68.coPaged.js polyfill breaks Polymer elementsThe Paged.js polyfill appears to break Polymer custom elements/web components. It may also break other web components. I suspect this is because Paged.js isn't copying the custom element's shadow DOM when it moves content around during p...The Paged.js polyfill appears to break Polymer custom elements/web components. It may also break other web components. I suspect this is because Paged.js isn't copying the custom element's shadow DOM when it moves content around during page layout.
Please see this test case project:
https://github.com/rgladwell/test-pagedjs-with-polymer
## Expected result
Polymer element should appear as follows:
![Screenshot_2019-06-01_at_10.30.29](/uploads/965159faf227d3e94f197883eb1bf09e/Screenshot_2019-06-01_at_10.30.29.png)
## Actual result
Instead Polymer elements appear without some content:
![Screenshot_2019-06-01_at_10.27.35](/uploads/973e6145a9772ddc334f71d6ca88ad94/Screenshot_2019-06-01_at_10.27.35.png)