As already mentioned above, I completely agree with the shortcomings of browsers for PDF conversion. The real fault line, in my opinion, is page-aware engines v

As already mentioned above, I completely agree with the shortcomings of browsers for PDF conversion. The real fault line, in my opinion, is page-aware engines versus Chrome, and neither side is free. Prince, Antenna House and PDFreactor are built around an actual page model (page breaks, running headers, cross-references, a real TOC), but they're perpetually chasing modern web and CSS support. Chrome is the opposite and weak at the page model. So you either pay for a licensed engine to get the page model, or you take Chrome's rendering and do the page, tagging and conformance work around it. And yes, that means owning the edge cases.