New issue
Advanced search Search tips

Issue 891845 link

Starred by 1 user
Status: WontFix
Owner:
justincohen@chromium.org
Closed: Oct 4
Cc:
kkhorimoto@chromium.org
ios-bugs@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: iOS
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Black bar is shown when opening Google Chrome links in landscape mode

Project Member Reported by shbarezer@chromium.org, Oct 3 
Version: 70.0.3538.44 Beta
Devices: iPhone Only
iOS: 10.3.3 Only
URL: news.google.com

Steps to reproduce:
1. Launch Chrome 
2. Change device mode to landscape
3. Go to Menu -> Settings -> Google Chrome -> Open Source Licenses
4. Go to Menu -> Settings -> Google Chrome -> Terms of Service

Observed results: Black bar is shown when opening Google Chrome links in landscape mode

Expected results: Black bar should not show, when opening Google Chrome links in landscape 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 Safari/Firefox: Firefox: No, Safari: No
Bug reproducible on current stable build (App Version, iOS Version): No
Bug reproducible on the current beta channel build (App Version, iOS Version): Yes

Link to video/image: https://drive.google.com/file/d/1yB7ui1uOKo_TpqQjbI88aKu7zEE5TjYd/view

Comment 1 by kkhorimoto@chromium.org, Oct 4

Cc: kkhorimoto@chromium.org
Components: UI>Browser
Labels: -Restrict-View-Google
Owner: justincohen@chromium.org
Status: Assigned (was: Untriaged)
Looks like there's an extra 20pts added to the header height.  Could be related to the GetStatusBar() stuff we're trying to get rid of; BVC might be adding the header offset mistakenly while the status bar is hidden.  I didn't think that we were hiding the status bar on landscape, so maybe that's the issue here?

Justin, sending your way in case you have some extra cycles to look at this; otherwise I can take a look later.

Comment 2 by justincohen@chromium.org, Oct 4

Status: WontFix (was: Assigned)
Given how rarely this would happen, that it's iOS10 only, and that it is self correcting, I'm going to mark this as WontFix.  If you think this is a part of larger issue, however, then please reopen, as when we eventually drop iOS10 we don't want to leave users with a broken state.
►

Sign in to add a comment