New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 833939 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

transform: scale behaves badly with browser zoom levels other than 100%, 200%

Reported by ge...@geoffarmstrong.com, Apr 17 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
1. Load the HTML file.
2. Change the browser zoom level (e.g. 110%, 125%, 75%).
3. Observe the "filling" doesn't match the red box at some zoom levels.

What is the expected behavior?
The filling should always fill the box.

What went wrong?
It doesn't fill the box on Chrome, but it does much better in Edge and Firefox.

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 65.0.3325.181  Channel: stable
OS Version: 10.0
Flash Version: 

Please fix.
 
square.html
437 bytes View Download
Labels: Needs-Triage-M65
Cc: sindhu.chelamcherla@chromium.org
Labels: M-68 FoundIn-68 Target-68 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on reported version 65.0.3325.181, on latest stable 66.0.3359.117 and on latest canary 68.0.3398.0 using Windows 10, Ubuntu 14.04 and Mac 10.13.3

This issue is seen from M-60. Hence considering this issue as Non-Regression and marking as Untriaged.

Thanks!

Comment 3 by e...@chromium.org, Apr 19 2018

Status: WontFix (was: Untriaged)
Browser zoom adjusts layout and is rounded to align with physical screen pixels to ensure crisp rendering.
Transforms do not.

Combining layout-affecting scaling (browser zoom) and transform scaling is not guaranteed to match. This is by design and is intentional as the two have very different use cases.

Similarly it will not align even at 100% on devices with a non-integear device scale factor.
Reading the spec, one would believe that they should match. They do match when testing on Firefox and Edge. Am I just misinterpreting the specification, or is this just a side effect of a performance optimization/shortcut that is only taken by Chrome? 

Sign in to add a comment