Two things that we have to probably make a decision about before we proceed here... (1) It looks like the Chrome print dialog's `custom-margins:0 0 0 0` setting *also* prints content right up to the edge of the page (gleefully drawing into unwriteable area area and getting clipped as a result). Whereas in the Firefox print dialog, `custom margins:0 0 0 0` gets shifted in to accomodate unwriteable area. If we're aligning with Chrome on what "None" meants w.r.t. the unwriteable area, we might want to consider aligning on the explicitly-zero-margins scenario as well (or make sure we've documented the distinction & made sure it's intentional). (2) If we do want to preserve a behavioral distinction between "Margins:None" vs. "Margins: Custom/0-0-0-0", we've got a bit of a problem, because we seem to represent them both the same way in the saved state, and we restore them both as "Margins:None" the next time you open the print dialog.
Bug 1681183 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Two things that we have to probably make a decision about before we proceed here... (1) It looks like the Chrome print dialog's `custom-margins:0 0 0 0` setting *also* prints content right up to the edge of the page (gleefully drawing into unwriteable area area and getting clipped as a result). Whereas in the Firefox print dialog, `custom margins:0 0 0 0` gets shifted in to accomodate unwriteable area. If we're aligning with Chrome on what "None" meants w.r.t. the unwriteable area, we might want to consider aligning on the explicitly-zero-margins scenario as well (or make sure we've documented the distinction & made sure it's intentional). (2) If we do want to create a behavioral distinction between "Margins:None" vs. "Margins: Custom/0-0-0-0" (as I was initially proposing in this bug), we've got a bit of a problem, because we seem to represent them both the same way in the saved state, and we restore them both as "Margins:None" the next time you open the print dialog.
Two things that we have to probably make a decision about before we proceed here... (1) It looks like the Chrome print dialog's `custom-margins:0 0 0 0` setting *also* prints content right up to the edge of the page (gleefully drawing into unwriteable area area and getting clipped as a result). Whereas in the Firefox print dialog, `custom margins:0 0 0 0` gets shifted in to accomodate unwriteable area. If we're aligning with Chrome on what "None" meants w.r.t. the unwriteable area, we might want to consider aligning on the explicitly-zero-margins scenario as well (or make sure we've documented the distinction & made sure it's intentional). (2) If we do want to create a behavioral distinction between "Margins:None" vs. "Margins: Custom/0-0-0-0" (as I was initially proposing in this bug), we've got a bit of a problem, because we seem to represent them both the same way in the saved state in about:config, and we restore them both as "Margins:None" the next time you open the print dialog.