Open
Bug 1434197
Opened 6 years ago
Updated 7 months ago
Box-shadow zoom
Categories
(Core :: Layout, defect, P3)
Tracking
()
NEW
People
(Reporter: nadhim.orfali, Unassigned)
References
Details
(Keywords: parity-chrome, parity-edge, regression)
Attachments
(1 file)
2.91 KB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36 Steps to reproduce: 1. Create a standard button. 2. Button contains a `box-shadow: inset 0 0 0 1px #808080`. 3. Load page. 4. Change browser zoom from 100% to 90%. See https://codepen.io/norfali/pen/aqbGdw for a working example. Windows 10. Issue occurs in Firefox 55 to 57 (latest). Actual results: Box-shadow isn't rendered correctly, see screenshot attached (the one on the right) Expected results: Box-shadow rendered correctly and works whether page zoom is 100% or 90%. Issue doesn't occur in Chrome.
Comment 1•6 years ago
|
||
Regression window: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=154a12a7a91c&tochange=7f5771d7934d Triggered by: 250cf47bfa76 Markus Stange — Bug 1181554 - Snap the spread radius for inset box shadows to device pixels.
Blocks: 1181554
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [parity-Chrome][parity-Edge]
Version: 57 Branch → 40 Branch
Comment 3•6 years ago
|
||
Mass bug change to replace various 'parity' whiteboard flags with the new canonical keywords. (See bug 1443764 comment 13.)
Keywords: parity-chrome,
parity-edge
Whiteboard: [parity-Chrome][parity-Edge]
Updated•6 years ago
|
Keywords: regression
I can still reproduce the error on Firefox 70.0.1 in Linux Mint 19.2.
Here is another minimal example to illustrate the issue: https://jsfiddle.net/c9tqyrab/
When the zoom changes from 100% to 90%, the box disappears entirely.
Note that I can only reproduce this on my 1920x1080 monitor. On a 4k display, this is reproducible by zooming out to 30%.
Still available in Firefox 72.0.2 (Windows). Problem appears with a 2560x1440 monitor
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•