Issue metadata
Sign in to add a comment
|
Location bar is overlapping with status bar in fullscreen mode. |
||||||||||||||||||||
Issue descriptionApp Version: 72.0.3626.8 beta iOS Version: 11.4.1, 12.1 Devices: iPhone 7, iPhone XR Steps to reproduce: 1. Launch iOS Chrome 2. Navigate to any webpage ex. cnn.com 3. Enter Fullscreen Observed Result: Location bar is overlapping with status bar in fullscreen mode. Expected Result: Location bar should not overlap with status bar in fullscreen mode. Number of times you were able to reproduce: 5/5 Bug reproducible after clean install: Yes Bug reproducible after clearing cache and cookies: Yes Bug reproducible on Chrome Mobile on Android: NA Bug reproducible on Safari/Firefox: Firefox: NA, Safari: NA Bug reproducible on the current stable build :M71, No Bug reproducible on the current beta channel build : M72, No about://versions Google Chrome 72.0.3626.8 (Official Build) beta(64-bit) Revision ca4162a9ba04... OS iOS User Agent Mozilla/5.0 (iPhone; CPU iPhone OS 12_1 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) CriOS/72.0.3626.8 Mobile/15E148 Safari/605.1 Command Line /var/containers/Bundle/Application/1BA9089E-5D9A-4CC7-BBE1-5231535C4A55/beta.app/Chrome --flag-switches-begin --disable-features=SlimNavigationManager --flag-switches-end Variations 1a0d11d4-2f9febdf 2b6ab552-ca7d8d80 b7e2524c-52931d5c 411c711e-3f4a17df 38eb801c-3f4a17df a582a1b8-ad75ce17 ab801be6-f23d1dea fd1d44dd-44df1bc1 68ccc549-ee63ae02 2d80427c-f23d1dea 587904d4-48b9f718 9b4c4257-592e7888 f79cb77b-3d47f4f4 e7b45bb7-3f4a17df 51b9b54d-f23d1dea 7345ea6-a50b0f4 494d8760-52325d43 3ac60855-486e2a9c f296190c-2624949d 4442aae2-6e597ede ed1d377-e1cc0f14 75f0f0a0-e1cc0f14 e2b18481-4ad60575 e7e71889-e1cc0f14 d0ed99bc-d0ed99bc Link to Image/Video: https://drive.google.com/file/d/1CiRaQAQNbIW47b-o-2sKtJnrF9yxQiw5/view
,
Dec 10
It seems to be triggered by an experiment on Canary. I was able to repro on one device and not in another one, with all the flags disabled on both. I have no idea which experiment could have triggered that.
,
Dec 10
I was able to repro with disabling SlimNavigationManager flag. 1. Navigate to any webpage ex. cnn.com 2. Enter Fullscreen before the page fully loads. https://drive.google.com/file/d/1OUp6S16bKz7URF0s633gO2K6mv9BaP4s/view
,
Dec 11
,
Dec 11
,
Dec 11
We were discussing this bug at leads.
,
Dec 11
I'll take a look at this after addressing the piper roll issues. Definitely a high priority bug. cc'ing Eugene since repro steps involve slim navigation manager.
,
Dec 11
Comment #3 says: "I was able to repro with disabling SlimNavigationManager flag.". Do you think we may need to have 2 separate fixes (with and without slim-navigation-manager)?
,
Dec 14
,
Dec 18
,
Dec 18
,
Dec 19
,
Dec 20
,
Dec 28
Marking as assigned for the time being since I'm not actively working on this because I can't reproduce locally. I'll work with testers when back in the office to figure out a solution for this.
,
Jan 2
shbarezer@ - Can you try to repro with the current beta? A user with 72.0.3626.28 reported something similar.
,
Jan 2
rkgibson@ is able to reproduce on its Canary (73.0.3643.0).
,
Jan 8
rkgibson: What are your repro steps?
,
Jan 8
Sorry, I don't have any repro steps. I just saw it once. And now it looks fine on the same version.
,
Jan 9
Marking as WontFix because we have no repro steps and it works on beta. Please reopen with repro steps if necessary.
,
Jan 9
Just tried on 72.0.3626.51 (most recent TestFlight) and cannot reproduce either.
,
Jan 9
Do we believe we know what was fixed here? I'm wary of walking away from this very serious issue without some idea about what changed to make this go away.
,
Jan 16
Reverting back to Assigned so we don't lose track of this. Not ReleaseBlocking. shbarezer@ was able to repro this (see comment 3). Are you still able to with the latest M72 beta release?
,
Jan 16
(6 days ago)
Tested on 72.0.3626.64 Beta, iPhoneXr iOS 12.1.2 issue is not repro.
,
Jan 16
(6 days ago)
Original report: 72.0.3626.8 beta TestFlight user report: 72.0.3626.28 Cannot repro: 72.0.3626.51 72.0.3626.64 Beta Is it possible that some changes cherrypicked between .28 release and .51 release fixed whatever issue it was?
,
Jan 16
(6 days ago)
Marking as available since I'm not actively working on this. Feel free to reassign to me if we get some repro steps. In c#18, rkgibson@ said that it couldn't even reproduce on the original report version as well, so I don't know if we have a reliable bisect to tell when this started/stopped reproducing. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by olivierrobin@chromium.org
, Dec 7Owner: kkhorimoto@chromium.org
Status: Assigned (was: Untriaged)