Printing 4x6 inch label is printing smaller than 4x6
Categories
(Core :: Printing: Output, defect)
Tracking
()
People
(Reporter: mrpcweb, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:96.0) Gecko/20100101 Firefox/96.0
Steps to reproduce:
When printing a 4x6 inch shipping label from the Wordpress dashboard to a Zebra label printer, the label that prints is smaller than 4x6.
Actual results:
The label that prints is smaller than the maximum available size for the print.
Expected results:
The label should print at the full label size of 4 x 6 inches.
Comment 1•4 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Printing: Output' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.
Comment 2•4 years ago
|
||
Do you have a website or file that repros this somehow? I wonder if the page is using @page { margin } or so.
Comment 3•4 years ago
|
||
This could also be caused by the printer reporting somewhat large unwriteable margins.
Google Chrome browser does not have this output issue. I suppose I can get page source before the end-user initiates a print.
Comment 5•4 years ago
|
||
The severity field is not set for this bug.
:jfkthame, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 6•4 years ago
|
||
Is it possible to save an example page that exhibits this problem as a file and attach here for investigation? Or is there a way we can try to reproduce this? I'm not familiar with "the Wordpress dashboard", printing shipping labels, etc., but that sounds like it's functionality of an e-commerce site of some kind...
Comment 7•3 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.
For more information, please visit auto_nag documentation.
Comment 8•2 years ago
|
||
Closing INCOMPLETE due to lack of a testcase that reproduces this. We can reopen if folks find reliable steps-to-reproduce.
Description
•