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

Issue 784643 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Table height issue when using scaling on high-dpi display (or when using zoom)

Reported by bug.iss...@gmail.com, Nov 13 2017

Issue description

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

Example URL:
https://jsfiddle.net/BugIssuer/bdkrvhon/

Steps to reproduce the problem:
1. Use 150% scaling in Windows and 100% zoom in Chrome, or 100% scaling in Windows and 150% zoom in Chrome
2. Navigate to https://jsfiddle.net/BugIssuer/bdkrvhon/
3. Observe that the table is 40.67px tall, instead of the expected 40px

What is the expected behavior?
The table height being 40px. The bottom part of the blue area being flush with the bottom part of the green area.

What went wrong?
Both table rows end up 1/3 of a pixel taller than expected, making the table 40.67px tall and the blue area extending below the green area.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 64.0.3266.0  Channel: n/a
OS Version: 10.0
Flash Version: 

I'm using 150% scaling in Windows 10 and 100% zoom in Chrome, but the same behavior can be observed by using 100% scaling in Windows 10 and 150% zoom in Chrome.

The same behavior can also be observed in Chrome Version 62.0.3202.94 (Official Build) (64-bit).
 
Components: -Blink UI>HighDPI
Labels: Needs-Triage-M64
Cc: divya.pa...@techmahindra.com
Labels: Triaged-ET M-64 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on reported version 64.0.3266.0, 62.0.3202.94 and latest Canary 64.0.3267.0 using Windows 10, Ubuntu 14.04 and Mac 10.12.6.

The issue is seen from M-50 (50.0.2641.0). Hence considering this issue as Non-Regression and marking it as Untriaged.


Looking back at earlier builds, the behavior changed between the following builds:
- It works as expected in Chromium 21.0.1175.0 (Developer Build 142269 Windows)
- It is broken in Chromium 21.0.1175.0 (Developer Build 142299 Windows)
Status: Archived (was: Untriaged)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment