Right now the shrinkToFit argument of the browsingContext.print command defaults to true. That even when a client specified the scale argument with a different value than 1. As result in Firefox the scaling is not applied at all.
When I check the print options of Safari I can see that Scale to fit paper size doesn't have any effect when a scaling value is set. Also Chrome behaves that way when using the system print dialog on MacOS. In it's own UI a Shrink to Fit option is not even visible. And in Firefox Shrink to Fit and Scale are options that are mutual exclusive.
Should we consider not applying shrinkToFit when scale has a custom value?
Note that this will also apply to WebDriver classic, and would require a separate PR.
Right now the
shrinkToFit
argument of thebrowsingContext.print
command defaults totrue
. That even when a client specified thescale
argument with a different value than1
. As result in Firefox the scaling is not applied at all.When I check the print options of Safari I can see that
Scale to fit paper size
doesn't have any effect when a scaling value is set. Also Chrome behaves that way when using the system print dialog on MacOS. In it's own UI aShrink to Fit
option is not even visible. And in FirefoxShrink to Fit
andScale
are options that are mutual exclusive.Should we consider not applying
shrinkToFit
whenscale
has a custom value?Note that this will also apply to WebDriver classic, and would require a separate PR.
CC @gsnedders @sadym-chromium, @jgraham