New issue
Advanced search Search tips

Issue 725054 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 26
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Inactive tabs crop off viewport on return

Reported by zach.r...@sproutsocial.com, May 22 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. Have a handful of tabs open
2. Sleep Mac and do not use overnight
3. Wake up Mac and go to any tab to find that they are all cropped off at a weird viewport
4. Resize the browser with that tab open and it then it fixes itself to go back to being the full viewport

What is the expected behavior?
When I return to the browser, the viewport of the site shouldn't be cropped down for some reason.

What went wrong?
Here is the cropped view. This is how it appears in every tab on every site. One I resize the browser at all, it then fixes itself and goes back to the full width/height like normal.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A 

Did this work before? Yes 

Does this work in other browsers? Yes

Chrome version: 58.0.3029.110  Channel: stable
OS Version: OS X 10.12.5
Flash Version: 

This seems to happen every morning when I wake up my Mac to begin working for the day. I don't know if there are more specific steps to take to fix this or how to reproduce the problem.
 
Screen Shot 2017-05-22 at 8.19.02 AM.png
161 KB View Download
I should also note that I have to resize the browser with each tab active to reset the viewport for that specific tab. One resize doesn't fix all the cropped viewports in each tab that is broken. So, when I go back to Chrome after my Mac was asleep, I'll have say 5 tabs that are cropped. I then have to resize the browser 5 times with each tab being active to fix the issue.
Another note I just discovered is that refreshing the page does NOT solve the issue. You have to actually resize the browser. to get the viewport to reset to normal.
Components: -Blink UI>Browser
Labels: Needs-Triage-M58
Can someone from browser team please look into this issue?

Thanks!!

Comment 6 by lgrey@chromium.org, May 26 2017

Cc: ccameron@chromium.org
[triage] ccameron@ is this a compositor issue?
Status: Assigned (was: Unconfirmed)
Yes, at some level we're not coordinating DSF here.

Assigning myself in case I get time to look at it. Feel free to steal from me if anyone wants.
If it helps with the bug, another thing I noticed to trigger it sometimes is it happens when I plug my Macbook into my Thunderbolt Display (non-retina). So, it could have something to do with going from my retina Mac to non-retina screen. In fact, I think I've only ever seen this happen when I'm plugging my Mac into a monitor and it goes from retina to non-retina. I just noticed when this happened on my retina screen, the screen actually had a slight delay and then corrected itself. So, I wonder if that same correction call is not being triggered when switched to a non-retina screen. Hope that helps some!
i am having a similar issue. i have recently installed windows 10 on my mac mid 2014 retina. I have an external monitor connected. When i open the chrome on external monitor, it looks fine, however when i drag it to my laptop monitor, the display gets cropped to 75%. i am attaching fine.png and issue.png to show the same.
currently using version 3.0.3239.108 (stable) on windows 10
fine.PNG
110 KB View Download
issue.PNG
165 KB View Download
Re #9, please file a separate bug for the Windows issue (Windows and macOS are very different how they handle retina screens, even on mac hardware).

Re #8, does this issue still happen on Chrome 63?
Status: Untriaged (was: Assigned)
Status: Available (was: Untriaged)
Cc: ligim...@chromium.org
Labels: Hotlist-DesktopUIChecked
Status: WontFix (was: Available)
*** UI Mass Triage ***

We were unable to reproduce this bug. If this bug still reproduces for you, 
please reopen or file a new issue. Thanks!

Sign in to add a comment