Bugzilla

The key thing here is that `size:10px` is smaller than the default margins.  So we end up with a negative page content area (after subtracting away the default margins from our 10px of page space), which Chrome disallows.

If you print-preview this in Chrome and choose "Margins: None", then they do honor the small page size (because now we have some greater-than-zero space for content.)

This seems to be bug 1807985.

(In reply to Thomas Wisniewski [:twisniewski] from comment #0)
> This is causing webcompat issues, as this was discovered while diagnosing why the print preview of www.theaa.com's route planner [shows nothing](https://github.com/webcompat/web-bugs/issues/117996) in Firefox's print preview.

Yikes.  Why would they be doing that. :-/  Anyway, good to know there's webcompat impact; until now, bug 1807985 was purely edge-case-handling.

The key thing here is that `size:10px` is smaller than the default margins.  So we end up with a negative page content area (after subtracting away the default margins from our 10px of page space), and Chrome disallows pages with <=0 content area, so it falls back to the default page size.

If you print-preview this in Chrome and choose "Margins: None", then they do honor the small page size (because now they have some greater-than-zero space for content).

This seems to be bug 1807985.

(In reply to Thomas Wisniewski [:twisniewski] from comment #0)
> This is causing webcompat issues, as this was discovered while diagnosing why the print preview of www.theaa.com's route planner [shows nothing](https://github.com/webcompat/web-bugs/issues/117996) in Firefox's print preview.

Yikes.  Why would they be doing that. :-/  Anyway, good to know there's webcompat impact; until now, bug 1807985 was purely edge-case-handling.