@liZe armphhhhhhhh......... I can be so dumb at times. That css files is basically a baseline from some frontend template I'm using throughout the project. I guess it just made its way there because.... well copy-past I guess. Removing it does solve the issue w/o really affecting the pdf (since I'm already specifying things I want to see there in my own css).
Well spotted. It probably set some width or something somewhere that weasy didn't like.
Fontconfig error: Cannot load default config file- anyone else had this and know what to do?
h1tags will be put in special pages called
h2tag is encounter, its content is put in a string named "heading" and we break before to have a new page https://github.com/CourtBouillon/weasyprint-samples/blob/d95ca0480c8ad1964065b89496541f7c73e5d251/report/report.css#L95-L99
file://URLs instead of
/static/URLs that are supposed to be served by the HTTP server
url_fetcherthat will translate
/static/…URLs into filenames and call the original
url_fetcherwith this filename