Hacker News new | ask | show | jobs
by baggy_trough 159 days ago
Yeah, the fact that Chrome doesn't support a lot of the CSS pagination properties is a problem. We have to use paged.js to do table of contents for example. And that requires controlling Chrome via puppeteer or the like. That's been a bit of a pain.
1 comments
gokulsiva 159 days ago
Yeah, that matches my experience too — Chrome gets you ~80% there, but the missing pagination primitives push you into extra layers like paged.js.

I’ve also hit issues with tables and page breaks.

Curious if TOC was the main blocker for you, or if there were other cases where Chrome alone didn’t hold up.

link
baggy_trough 158 days ago
That's really the main one I remember.
link