Guillaume Ayoub
Guillaume Ayoub
> Is there any estimate on when `display: contents` may be supported? No, itâs not on our roadmap yet.
Thanks a lot. Thatâs related to flex layout, weâll check that everything is OK when the flex module is rewritten.
> Thatâs related to flex layout, weâll check that everything is OK when the flex module is rewritten. No, actually thatâs not related to flex at all.
Minimal sample: ```html t tt ```
Itâs now fixed and tested, will be included in v64.1 that will be released soon!
Hi! Thanks for the report. Weâll get in touch with the maintainer to know if we could maintain the package. Code shouldnât change much, but we can at least close...
We tried to contact the maintainer, but she didnât answer yet. Weâll try other channels.
Hi! > In our app we generate HTML reports which sometimes result in upto 100MB+ of html files. Then you could probably benefit from our [professional support](https://weasyprint.org/#support). :smile: > By...
The problem comes from: https://github.com/Kozea/WeasyPrint/blob/603d87c9783150818f49e3929baece123d4e5026/weasyprint/layout/grid.py#L270-L271 Calling `min_content_width` on text is quite long, because we need to render all the words one by one to find the longest. This function is...
Thatâs actually extremely long because you use `word-break: break-all` for almost all your text, so each ~word~ _letter_ is actually rendered separately to find the min-width of your grid items...