Issue metadata
Sign in to add a comment
|
exit from fullscreen leaves grey strip over 2/3 of main toolbar (navigation, URL, extension dock)
Reported by
rjvber...@gmail.com,
Nov 6 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.75 Safari/537.36 Steps to reproduce the problem: 1. Open any site that has an element that can make itself fullscreen, e.g. any video player, or even a smugmug page (https://bill-and-kathi.smugmug.com/Norging-to-Georgia-Nov-2017/n-5K5Jww/i-6mTqkZm) 2. go into fullscreen mode using the widget the pages provides to that purpose 3. exit from fullscreen mode by hitting Escape or the appropriate widget on the page What is the expected behavior? window should be restored as it was What went wrong? a grey strip covers about 2/3 of the main toolbar, blocking the view of the URL, navigation buttons and extension icons. It appears to be transparent to focus/click events. See the attached screenshot taking after coming back from fullscreen mode on the smugmug site given in step 1). Did this work before? Yes I updated from 60.0.3112.78 where this still worked fine. Chrome version: 62.0.3202.75 Channel: stable OS Version: OS X 10.9.5 Flash Version: Shockwave Flash 27.0 r0 Tearing the tab(s) off into a new or existing window fixes the glitch, for those tabs. The issue doesn't occur when using the "zoom/fullscreen" action from the toolbar or View menu; those use native fullscreen mode. Once I am in native fullscreen mode I can use the on-site widget to put the page content in and out of fullscreen mode; in that case the glitch does NOT occur. I have the system option "spaces have separate screens" DEactivated (so native fullscreen mode isn't an option for me as it blacks out all screens).
,
Nov 6 2017
,
Nov 6 2017
Hello sdy@: This issue here should be already fixed in 62.0.3202.75 regarding issue 781556 , right? But the reporter is still seeing this with that build :-( Any ideas? May be because the reporter is using Mac OS X 10_9_5 ? Thanks.
,
Nov 6 2017
These issues may be related but I don't think they're one and the same. In my case the tabs bar is unaffected, and nothing is disabled as far as I can tell. It looks most like a drawing artefact, as if the tabbar background bleeds or something goes wrong with a compositing operation. FWIW, I'm on a MacBookPro8,1 with a Core i7 and HD3000 graphics.
,
Nov 7 2017
Hi, I don't know if this is related, but I just realise that Chrome's windows don't have a border anymore, nor a drop shadow behind them. Looks subtly but really weird. R.
,
Nov 7 2017
Can you please attach a screenshot from your mentioned issue? Thanks.
,
Nov 8 2017
Here's a screenshot of the no-border-nor-shadow issue, if that's what you meant. A screenshot of the main issue is already attached as far as I can see. As to that border/shadow issue: it seemed to affect a single window only, behaving much in the same manner the grey bar does. I could drag tabs off into a new window that behaves as it should. The only difference is that I don't know how to reproduce this weird state. As I said, I don't know if these are related; both do seem to hint at some kind of internal state, not just an issue that expresses itself at the graphics driver level (i.e. it cannot be repaired with an appropriate sequence of actions resulting in rendering operations that restore the view as it should be). Minimising, hiding the entire app, dragging the window across Spaces or toggling it to and from native fullscreen mode, none of that affected the border/shadow issue, as it doesn't affect the grey bar once it's appeared. I did see a transient drawing (stencilling?) glitch yesterday; a window containing a paused streaming video player (youtube IIRC) showed text from another browser window that had covered it when I brought the player page back to the front. That alien content scrolled with the page view but was cleared when the scrolled-off portion was scrolled back into view. I haven't been able to reproduce this yet, so I'll just mention it here for now. FWIW that player page had not been made fullscreen.
,
Nov 9 2017
Unfortunately I haven't had any luck in getting this to happen. I attached a screen recording so you can see. Maybe I missed a step? If it still happens to you, it would be super helpful if you could take a screen recording with QuickTime Player showing chrome://version and the issue. (We're also *just* starting to explore the idea of phasing out 10.9 and 10.10 support in Chrome. For what it's worth, it looks like your machine can run current macOS :).)
,
Nov 9 2017
I think this might share a root cause with another issue. Maybe we can work with the other reporter to find a reliable way to trigger it.
,
Nov 9 2017
By the way, I think the graphics issues are worth filing as a separate bug!
,
Nov 9 2017
I'll try to do as you say, if necessary filming with my phone ;) Either way, is there a way to start a 2nd Chrome session without logging in as another user, a truly independent one where I can do a full reset of all settings and deactivate all extensions? I am aware of other cases of unexplained behaviour that no one can reproduce and that I think must thus be a result of some personal combination of Chrome settings, extensions and extensions settings. Another explanation for not being able to reproduce is that it's indeed an issue that is related to my GPU and/or driver for it. (I know my hardware can run the latest Mac OS. I also know upgrading and getting to a state where things work the way *I* want can take, well, months, and the big unknown is how well my hardware will run that latest OS. It's got "only" 12Gb RAM, for instance, and I need that for myself, not for the OS ;) )
,
Nov 27 2017
Sorry for the delay. If you're comfortable with a terminal, you can run Chrome like this: /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=Desktop/'Temporary Chrome Profile' It'll store its data in a folder called "Temporary Chrome Profile" on your desktop, which will be totally separate from your usual Chrome "instance". |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 Deleted