Gray strip appears at the top of the screen |
||||||
Issue descriptionChrome Version: 65.0.3317.0 OS: macOS 10.11 and older What steps will reproduce the problem? (1) Have multiple monitors connected. (2) Turn off "Displays have separate Spaces" in System Preferences (and log out/in if needed). (3) Enter content fullscreen by visiting this page and clicking anywhere: data:text/html,<body onclick="this.webkitRequestFullScreen()"> (4) Press esc to exit content fullscreen. (5) Click the window zoom button to enter normal fullscreen. What is the expected result? No gray strip at the top of the window. What happens instead? There is a gray strip at the top of the window. Similar root cause to issue 779082 , and I regressed this in 1b761b8d95af216fbd403262ac001ab362e7a6b3.
,
Jan 23 2018
,
Jan 24 2018
Hey shrike@. How would you feel about merging dec06ed3705dc353977df4441eed7cb16d170927 to M65? It turns out that it fixes this issue too. (I was about to upload my own patch and hit a merge conflict!)
,
Jan 24 2018
I'm nervous about doing that. I discovered, after several passes, a number of spots in the code where engineers assumed the window controller/delegate was the bwc. It's difficult to know if I found all those spots, which is part of why I waited to land the cl until after branch, to get maximum airtime on Canary. I'm not sure what this means for your patch :-(.
,
Jan 24 2018
No worries. This bug turns out to not be a regression and has been around for a few milestones, so waiting one more should be okay thanks!
,
Jan 24 2018
,
Jan 24 2018
> I'm nervous about doing that. I discovered, after several passes, a number of spots in the code where engineers assumed the window controller/delegate was the bwc. It's difficult to know if I found all those spots, which is part of why I waited to land the cl until after branch, to get maximum airtime on Canary. For example, Issue 805282 .
,
Mar 30 2018
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by sdy@chromium.org
, Jan 23 2018