Printing on Chrome generates way too many pages

[pradyunsg]

Discussed in #352

With an empty documentation set, open a generated page in Chrome and try printing the page. Notice that Chrome decides that there are 5 digits (order of 10,000) of pages to print.

[pradyunsg]

Also reproducible on https://pradyunsg.me/furo/. (as of https://github.com/pradyunsg/furo/tree/d6b217f8bb021f137928aa30f1b41e829e87d73f)

[berellevy]

don't know if this detail helps but the issue still exists even when I select the text that I want to print.

my thought is that right clicking selected text and choosing print would send less data to the browser to but tbh I don't know how print works.

Anyway, hope I was helpfull.

psf/black#2866

[benjaminpick]

If somebody wants to debug this - I had a similar problem in my project and the culprit was some combination of different flexboxes...
Here is a bug ticket about it: https://bugs.chromium.org/p/chromium/issues/detail?id=640187

[chapkom]

I hope this helps.

I ran into this issue on one of my coding projects for work. It turns out the culprit was a flex styled div that was completely empty.

It started printing normally once I updated my project to output a non breaking space in the div.

Chrome appears to have some issue rendering flexboxes without inner text for print.

[pradyunsg]

This got fixed in #319, which hid one such flexbox-without-inner-text objects. Thanks for providing the context on why this happened in your projects @benjaminpick and @chapkom!

It makes me a bit more comfortable, since your comments provided the missing piece of information I needed to have a better understanding of why #319 fixed this issue. :)