"Scale" field on print preview has an unwanted white gap on Nova
Categories
(Toolkit :: Themes, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox155 | --- | affected |
People
(Reporter: selim, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
104.12 KB,
image/jpeg
|
Details |
scale-nova.jpg
Steps to reproduce
- Press Ctrl+P to print any page.
- Observe the borders of the "Scale" setting on the right pane.
|
||
Comment 1•1 month ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Printing: Output' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 2•1 month ago
|
||
This is a Firefox front-end issue.
|
||
Comment 3•29 days ago
|
||
I can see this too. In fact, I can see the same issue on the "Number of copies" input. It looks slightly different in dark mode, like the up and down buttons are clipping through the right side of the input box. These button elements appear to be -moz-number-spin-up and -moz-number-spin-down, whose style appears to be defined here, so I'm going to redirect this bug to the owners of that code.
|
||
Comment 4•26 days ago
|
||
I think this should go back to the front-end team for consideration; it's basically a design issue. It's happening because of how the <input type=number> field is being styled -- the use of border-radius doesn't allow enough space for the background of the spinner buttons, which then overlaps the rounded border.
Some possible workarounds: ensure that the buttons have a transparent background? (Not sure where that would be specified.) Or add some padding-inline-end to the <input>, so that they're inset from the edge sufficiently that they don't collide with the curves. Maybe make the buttons themselves narrower, as they seem to have quite a bit of padding beside the actual symbols (but that might make them harder to hit). Or apply clipping to them so that their rendering follows the curve of the <input>'s border.
|
||
Comment 6•26 days ago
|
||
Frontend team is already looking at this in bug 2059515.
Looks like this bug was filed a few days before that one, but I'm going mark this one as a duplicate, since bug 2059515 is already assigned/triaged by frontend folks, and has an associated Jira ticket, etc.
Description
•