New issue
Advanced search Search tips

Issue 883678 link

Starred by 1 user
Status: Duplicate
Merged: issue 377847
Owner: ----
Closed: Sep 13
Cc:
style-bugs@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome on Windows 8.1 with Zoom set to 125% (on OS level) causes CSS issues

Reported by liubomir...@gmail.com, Sep 13 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Open the test file
2. Inspect the #container element
3. In dev tools - it would say the actual width is set to 377.6px, meanwhile the content is not resized, which causes the content to incorrectly float on the left and creates a new row

What is the expected behavior?
All 3 items should fit in the #container.

What went wrong?
On Windows 8.1, with Windows's OS zoom set to 125% (device per pixel ratio is 1.25) Chrome (and only Chrome, FF and IE works fine) alters the set width of the #container to a width lower then the desired, without altering the child elements's width, which causes issues.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 69.0.3497.92  Channel: stable
OS Version: 8.1
Flash Version: 

This definitely feels like a Chrome bug, since it basically makes the rendering of simple float'ed elements in a width's predefined container (with display: table) inconsistent across OSes and browsers (e.g. it fails in Chrome + Win8.1 + OS Zoom set to 125%).
win81test.html
1012 bytes View Download
chrome.png
226 KB View Download
ff.png
50.1 KB View Download
windows settings.png
234 KB View Download

Comment 1 by e...@chromium.org, Sep 13

Mergedinto: 377847
Status: Duplicate (was: Unconfirmed)
This is due to table layout and floats rounding differently. Effectively tables always round to full pixel values while block-flow layout (including floats) does not.

This is a known problem and happens regardless of windows zoom setting if you use chrome full page zoom.

Fixing this is tracked in issue 377847 but it's going to be at least another year. In the mean time try to avoid mixing table and non-table layout.
►

Sign in to add a comment