This doesn't seem to be a regression. I tried a few old Nightlies and observed "Actual Results" in all of them: 2020-01-01 2017-01-01 2013-01-01 I also see "Actual Results" in Safari (14.0.3) and Chrome 88. I also think this "Paper Handling" piece of UI is controlled by the OS, not by us (it's a piece of the system print dialog), so I'm not sure we have any control over it. So, to the extent that there's a bug here (which I'm not entirely sure about), I don't think it's a bug in Mozilla code.
Bug 1685509 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
This doesn't seem to be a regression. I tried a few old Nightlies and observed "Actual Results" in all of them: 2020-01-01 2017-01-01 2013-01-01 I also see "Actual Results" in Safari (14.0.3) and Chrome 88. I also think this "Paper Handling" piece of UI is controlled by the OS, not by us (it's a piece of the system print dialog), so I'm not sure we have any control over its contents. So, to the extent that there's a bug here (which I'm not entirely sure about), I don't think it's a bug in Mozilla code.
This doesn't seem to be a regression. I tried a few old Nightlies and observed "Actual Results" in all of them: 2020-01-01 2017-01-01 2013-01-01 I also see "Actual Results" in Safari (14.0.3) and Chrome 88. I also think this "Paper Handling" piece of UI is controlled by the OS, not by us (it's a piece of the system print dialog), so I'm not sure we have any control over the details of how it renders. So, to the extent that there's a bug here (which I'm not entirely sure about), I don't think it's a bug in Mozilla code.
This doesn't seem to be a regression. I tried a few old Nightlies and observed "Actual Results" in all of them: 2020-01-01 2017-01-01 2013-01-01 I also see "Actual Results" in Safari (14.0.3) and Chrome 88. I also think this "Paper Handling" piece of UI is controlled by the OS, not by us (it's a piece of the system print dialog), so I'm not sure we have any control over the details of how it renders. So, to the extent that there's a bug here (which I'm not entirely sure about given that we're matching other browsers), I don't think it's a bug in Mozilla code.