NI means "need info" which is an internal abbreviation we use to request information (checkbox below the text box), but that was directed to a developer from the component I've set the bug on, not to you.
In any case, I have used your last test case to compare the result of Firefox Release v81 and Firefox Release v83 and I have noticed the difference you are talking about, however, the why it looks in Print Preview is always the same as it looks after being printed to PDF. (This is information for developers picking this up.
Considering this is a regression, I have performed a regression range investigation using mozregression and I have come up with this:
2020-12-09T23:32:12: INFO : platform_version: 82.0a1
2020-12-09T23:32:16: INFO : Can't find symbol 'eglSwapBuffersWithDamageEXT'.
2020-12-09T23:39:17: INFO : Narrowed inbound regression window from [202c4cce, e5d999b6] (4 builds) to [a153feae, e5d999b6] (2 builds) (~1 steps left)
2020-12-09T23:39:17: DEBUG : Starting merge handling...
2020-12-09T23:39:17: DEBUG : Using url: https://hg.mozilla.org/integration/autoland/json-pushes?changeset=e5d999b6f07f3d8abb29d4a6117b5416f2141707&full=1
2020-12-09T23:39:29: DEBUG : Found commit message:
Bug 1665001 - Don't allow custom page margins to go under the unwriteable margin. r=jwatt
Differential Revision: https://phabricator.services.mozilla.com/D90231
2020-12-09T23:39:29: DEBUG : Did not find a branch, checking all integration branches
2020-12-09T23:39:29: INFO : The bisection is done.
2020-12-09T23:39:29: INFO : Stopped
Bug confirmed on Windows 10 and Ubuntu 20.
Bug 1679041 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
NI means "need info" which is an internal abbreviation we use to request information (checkbox below the text box), but that was directed to a developer from the component I've set the bug on, not to you.
In any case, I have used your last test case to compare the result of Firefox Release v81 and Firefox Release v83 and I have noticed the difference you are talking about, however, the way it looks in Print Preview is always the same as it looks after being printed to PDF. (This is information for developers picking this up.
Considering this is a regression, I have performed a regression range investigation using mozregression and I have come up with this:
2020-12-09T23:32:12: INFO : platform_version: 82.0a1
2020-12-09T23:32:16: INFO : Can't find symbol 'eglSwapBuffersWithDamageEXT'.
2020-12-09T23:39:17: INFO : Narrowed inbound regression window from [202c4cce, e5d999b6] (4 builds) to [a153feae, e5d999b6] (2 builds) (~1 steps left)
2020-12-09T23:39:17: DEBUG : Starting merge handling...
2020-12-09T23:39:17: DEBUG : Using url: https://hg.mozilla.org/integration/autoland/json-pushes?changeset=e5d999b6f07f3d8abb29d4a6117b5416f2141707&full=1
2020-12-09T23:39:29: DEBUG : Found commit message:
Bug 1665001 - Don't allow custom page margins to go under the unwriteable margin. r=jwatt
Differential Revision: https://phabricator.services.mozilla.com/D90231
2020-12-09T23:39:29: DEBUG : Did not find a branch, checking all integration branches
2020-12-09T23:39:29: INFO : The bisection is done.
2020-12-09T23:39:29: INFO : Stopped
Bug confirmed on Windows 10 and Ubuntu 20.