未接收(承诺)错误:项目不属于列表paged.polyfill.js错误
我正在使用PAGEDJS将页脚和标头添加到我们网站中转换为PDF的HTML模板中。该代码一直在工作一个星期,直到今天早上出现此错误。
这是我的代码:
<script src="https://unpkg.com/pagedjs/dist/paged.polyfill.js"></script>
<script>
class MyHandler extends Paged.Handler {
constructor(chunker, polisher, caller) {
super(chunker, polisher, caller);
}
beforeParsed(content) {
// Chapters Counter
$("head").append(`
<style>body{counter-set: chapters ${content.querySelectorAll(".chapter").length};}</style>
`);
}
afterPageLayout(pageFragment, page){
//if pageFragment does not have a page class, delete it
if(pageFragment.querySelectorAll(".page").length == 0){
console.log("Hiding page!");
console.log(pageFragment);
pageFragment.setAttribute("style", "display:none;");
}
}
}
Paged.registerHandlers(MyHandler);
</script>
任何帮助都将不胜感激。
I'm using PagedJS to add footers and headers to the html templates that we convert to PDF in our website. The code's been working fine for a week until this morning when this error keeps popping up.
This is my code:
<script src="https://unpkg.com/pagedjs/dist/paged.polyfill.js"></script>
<script>
class MyHandler extends Paged.Handler {
constructor(chunker, polisher, caller) {
super(chunker, polisher, caller);
}
beforeParsed(content) {
// Chapters Counter
$("head").append(`
<style>body{counter-set: chapters ${content.querySelectorAll(".chapter").length};}</style>
`);
}
afterPageLayout(pageFragment, page){
//if pageFragment does not have a page class, delete it
if(pageFragment.querySelectorAll(".page").length == 0){
console.log("Hiding page!");
console.log(pageFragment);
pageFragment.setAttribute("style", "display:none;");
}
}
}
Paged.registerHandlers(MyHandler);
</script>
Any help would be greatly appreciated.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我身边的问题是
删除后直接HTML包装器中的CSS规则,错误消失了
The problem on my side was this css rule in the direct html wrapper
after removing it the error was gone