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

Issue 713434 link

Starred by 2 users
Status: Duplicate
Merged: issue 843354
Owner:
osh...@chromium.org
Closed: Jun 2018
Cc:
█ marc...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Maximized windows do not cover the bottom row of pixels on non-default resolutions

Project Member Reported by dnschn...@chromium.org, Apr 19 2017 
Google Chrome   41.0.2272.8 (Official Build) dev 
Revision        08429e004dec7ee893418516e3334a4f2f757903 
Platform        6680.5.0 (Official Build) dev-channel samus

Google Chrome   57.0.2987.146 (Official Build) (64-bit)
Revision        0
Platform        9202.64.0 (Official Build) stable-channel samus

What steps will reproduce the problem?
(1) On Samus, use a non-default scaling
(2) Place a window such that it takes up a portion of the width of the screen, and move it down so that it goes passed the bottom of the screen.
(3) Open a new window and maximize it.

What is the expected result?
Window in (2) is completely occluded by (3).

What happens instead?
The bottom row of pixels of the screen passes through and (2), along with the desktop, can be seen.


From marcheu@:
"Changing the scaling in the display UI fixes it. It happens at 800x531, 1440x956, 1600x1062, not with the other scaling factors. 

oshima@ this sounds like your alley?"

Comment 1 by adamrodriguez@google.com, Jun 25 2018 

Saw this again today. This is a dupe of : https://b.corp.google.com/issues/35545307

which was filed in 2015...

Can we fix? it looks pretty bad

Comment 2 by osh...@chromium.org, Jun 25 2018

Mergedinto: 843354
Status: Duplicate (was: Assigned)
We've been working on new scaling and the issue is slightly different from old issue.
►

Sign in to add a comment