It should be required to run these tests for these libraries. It's really frustrating to have to discover it trying to make it work.

CSS coverage is stated in [1]. It should be required to do minimal assessment before entitledly posting on HN.

[1]: https://github.com/plutoprint/plutobook/blob/main/FEATURES.m...

I'm not sure your point. CSS print conformance is extremely complex. There is a fairly well known open source test suite, that's fully dynamic, that can be run with visual outputs, fail/pass metrics etc. That would give an interested new user a much better grounding if the library is worth using, considering there are already several other options.