[User Feedback - Stable] Mac - minimize / maximize buttons are overlapping with the leftmost tab |
|||||
Issue descriptionChrome Version: 69.0.3497.100 OS: Mac OS X: 10.13.6 We've seen two different user reports that the minimize / maximize buttons are overlapping with the leftmost Chrome tab and are not responsive. See screenshot. What happens instead? http://feedback/#/Report/85670568143 http://feedback/#/Report/85664510723
,
Sep 28
one has a possible hint: "When i click the green button to make the chrome window maximise the three toggles jumped on top of the new tab and the screen does not maximise" The green button should be fullscreen, not maximize (unless holding alt). I wonder if this is related to something like BetterTouchTool injecting code to drop the window out of fullscreen in a racy way that makes the tabstrip think it is fullscreen, but the frame think it is not. (atotic@: do you use a tool like this?)
,
Sep 28
I have a pretty simple setup, no fancy extensions of any kind. I often hold down ctrl/option (too many terminal windows). I spent some time trying to reproduce, no go. I did upgrade to Mojave since bug report.
,
Sep 28
atotic@ Thanks for the update. Tested this issue on Mac OS 10.13.3 on the reported version 69.0.3497.100 and the latest Canary 71.0.3564.0 and unable to reproduce the issue. Could not observe the minimize/maximize buttons overlap on minimizing/maximizing the window repeatedly. As per comment #3, as the issue is no longer reproducible, can you please confirm if this issue can be closed? Thanks...
,
Sep 28
Mac triage: over to sdy@ :)
,
Oct 12
Hi, I am able to reproduce this issue consistently. Chrome: Version 69.0.3497.100 (Official Build) (64-bit) macOS High Sierra 10.13.6 It occurs when I move Chrome's window from my Mac's display to the external monitor and then try to maximize.
,
Oct 12
Ouch, I restarted the Mac and now I am unable to reproduce following same exact steps.
,
Nov 15
** Mass UI Triage ** We were unable to reproduce this bug Mac 10.13.6 with chrome Stable #70.0.3538.102, Canary #72.0.3610.0. If this bug still reproduces for you, please reopen or file a new issue. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by meh...@chromium.org
, Sep 27