Issue metadata
Sign in to add a comment
|
macOS fullscreen mode missing window operation buttons
Reported by
zachary....@westwing.pl,
Jun 27 2018
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3472.3 Safari/537.36 Steps to reproduce the problem: 1. Open a browser window 2. Enter macOS full screen mode (green button on the window or ^⌘F) 3. Make sure that toolbar is always visible (View-"Toolbar Always visible" or ⇧⌘F) 4. Try closing, minimizing or windowing the app next to the tabs What is the expected behavior? The buttons should be with the toolbar What went wrong? Buttons are unavailable Did this work before? Yes 68 Chrome version: 69.0.3472.3 Channel: dev OS Version: OS X 10.13.5 Flash Version:
,
Jun 28 2018
Unable to reproduce the issue on chrome reported version# 69.0.3472.3 using Mac 10.13.5 with steps mentioned below: 1) Launched chrome reported version and made chrome window to full screen(or by using ^+⌘+F) 2) Clicked on ⇧+⌘+F, to make sure tool bar is visible 3) Able to see Closing, minimising buttons to the side of tabs @Reporter: Please find the attached screencast for your reference and let us know if we missed anything in reproducing the issue, provide your feedback on it which help in further triaging the issue. Thanks!
,
Jun 28 2018
The same problem. 68.0.3440.42. Looks like just autoupdated from previous version, no additional actions needed to reproduce.
,
Jun 28 2018
Same here, my Chrome on my MacBook auto-updated itself to 68.0.3440.42 and now fullscreen is broken (no tabs or address bar) like above.
,
Jun 28 2018
viswa.karala@, can you please test M-68?
,
Jun 29 2018
Unable to reproduce the issue on chrome version# 68.0.3440.42 using Mac 10.13.5 with steps mentioned below: 1) Launched chrome reported version and made chrome window to full screen(or by using ^+⌘+F) 2) Clicked on ⇧+⌘+F, to make sure tool bar is visible 3) Able to see Closing, minimising buttons to the side of tabs @Reporter: Please find the attached screencast for your reference and let us know if we missed anything in reproducing the issue. Thanks!
,
Jun 29 2018
I did some testing and it has something to do with #top-chrome-md flag. I had it set to "Normal" and so far it meant native Mac UI in Chrome main menu and gray bookmarks bar menus. After this latest update, suddenly Chrome menu changed to some custom View with white background and a lot of whitespace. I changed this to "Default" today and it restored old UI and fixed fullscreen issue. But when I changed it to "Normal", and then again to "Default", the UI stayed custom and fullscreen issue is still there.
,
Jun 29 2018
After manually restarting Chrome once again (with #top-chrome-md set to "Default") old ui (and working fullscreen) come back. So it seems that "Normal" setting for #top-chrome-md was broken in 68.0.3440.42.
,
Jul 3
It's totally broken as well if you set it to "Refresh". The toolbar doesn't even show up in Full Screen mode.
,
Jul 6
,
Jul 9
I have a similar issue (same issue as other commenters) on current beta channel release (68.0.3440.42) where going to fullscreen hides the address bar completely (not even reachable with Cmd+L). Normal MacOS 10.13.5 (17F77) on MacBook Pro 15'' (late 2013). Steps to reproduce: 1. Install Chrome 68.0.3440.42 2. Open Chrome 3. Go Fullscreen (doesn't matter whether via ctrl+cmd+f or via the button in top left corner) --> Animation for fullcsreen transition plays, and at the end, the adress bar and tabs-bar completely vanishes. Can't be brought back by moving mouse to top of screen, it's just gone. Cmd + L doesn't work. Trying to type into the adress window in the center of the standard 'New Tab' window also doesn't work at all ... no input is registered and a tooltip appears saying "Please enter URL".
,
Jul 9
Over to weili for macviews fullscreen issues.
,
Jul 16
Comment 11 findings are reproducible using Chrome 69.0.3493.0 on MacOS 10.14
,
Nov 20
** Mass UI Triage ** We were unable to reproduce this bug in latest Mac Canary #72.0.3616.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 viswa.karala@chromium.org
, Jun 27 2018