New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 689115 link

Starred by 8 users

Issue metadata

Status: Fixed
Owner:
Last visit > 30 days ago
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

[Regression][Fullscreen] The Tabstrip never appears (or disappears immediately) when "Hide always Toolbar in Fullscreen Mode" is selected and you open a new tab

Project Member Reported by meh...@chromium.org, Feb 6 2017

Issue description

Chrome Version: 58.0.3004.0 canary (64-bit) 
OS: OSX 10.11.6

What steps will reproduce the problem?
(1) Open a Chrome window
(2) Go into Fullscreen Mode
(3) Select "Hide always Toolbar in Fullscreen Mode"
(4) Open some new Tabs

What is the expected result? What happens instead?
The Tabstrip never appears (or appears immediately) when I open a new tab.

Please use labels and text to provide additional information.
A screencast is attached.

+Needs-Bisect label to find the correct regression.

 
bug_fullscreen.mov
875 KB Download
Components: UI>Browser>FullScreen
Labels: ReleaseBlock-Stable
Summary: [Regression][Fullscreen] The Tabstrip never appears (or disappears immediately) when "Hide always Toolbar in Fullscreen Mode" is selected (was: [Regression][Fullscreen] The Tabstrip never appears (or appears immediately) when "Hide always Toolbar in Fullscreen Mode" is selected)
Title correction: (or *dis*appears immediately)
Cc: sureshkumari@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Mac-10.12.2 using chrome stable version 56.0.2924.87 ,canary 58.0.3006.0 and Reported version 58.0.3004.0 with the steps mentioned above.

Please find the attached screencast and please let us know if anything missed here to reproduce the issue.

Thanks..
689115.mov
6.0 MB Download
Labels: -Needs-Feedback
Hello sureshkumari@,

sorry, step (4) was not clear enough described. You have to put the cursor somewhere on the web content area and press CMD-T to open the new tabs.

This means now:

What steps will reproduce the problem?
(1) Open a Chrome window
(2) Go into Fullscreen Mode
(3) Select "Hide always Toolbar in Fullscreen Mode"
(4) Move the cursor somewhere on the page, so that the Toolbar area disappears
(5) Open some new Tabs with CMD-T

Cc: pinkerton@chromium.org shrike@chromium.org
Labels: M-58
Adding milestone for RBS label. 
Labels: -Pri-1 -Needs-Bisect -Type-Bug-Regression Pri-2 Type-Bug
Able to reproduce the issue on Mac-10.12.2 using Chrome stable version 56.0.2924.87 and canary 58.0.3007.0 with the steps mentioned in comment#4.

This is Non-regression issue, Observed from M51 #51.0.2662.0 and confirming this issue to get more inputs from Dev team.

Please find the attached screencast for reference.

Note: From M30 to M50 there is no Option "Hide toolbar in full screen".

Thanks..
Issue-689115.mov
5.2 MB Download

Comment 7 by meh...@chromium.org, Feb 12 2017

Labels: -Type-Bug -Pri-2 Pri-1 Type-Bug-Regression
Summary: [Regression][Fullscreen] The Tabstrip never appears (or disappears immediately) when "Hide always Toolbar in Fullscreen Mode" is selected and you open a new tab (was: [Regression][Fullscreen] The Tabstrip never appears (or disappears immediately) when "Hide always Toolbar in Fullscreen Mode" is selected)
It was definitely broken in Chrome 58.

Here is the regression range: https://chromium.googlesource.com/chromium/src/+log/891d0d69870da1d4470170dde087afe354e01e15..ef1da2f145faf9e26d457fdf39fe5c607506ccb1

spqchan@: Probably broken with https://codereview.chromium.org/2666213003

If you need more information, please let me know.

Thanks!

Comment 8 by ajha@chromium.org, Feb 21 2017

Cc: rsesek@chromium.org
This is still reproducible on the latest canary(58.0.3018.0) of Mac OS 10.12.2.

spqchan@: Could you please take a look at this and update the thread.


Status: Started (was: Assigned)
This is still reproducible on the latest canary(58.0.3026.0) of Mac OS 10.12.3.

spqchan@: Could you please take a look at this and update the thread.
Gentle ping to get an update on this as it was marked as a blocker.
Thank you!!
Labels: Merge-Request-58
Labels: M-57
Today I installed Chrome 57 Stable and I noticed this bug there too. 

So I checked https://codereview.chromium.org/2666213003, which caused this issue and I noticed that this CL was merged to M57 later with https://codereview.chromium.org/2671073002.

Therefore I am also adding M57 to this bug. Maybe it is possible to merge this fix after landing in M58 to land this in M57 too?

Thank you!
Cc: krajshree@chromium.org meh...@chromium.org
 Issue 699508  has been merged into this issue.
Project Member

Comment 16 by sheriffbot@chromium.org, Mar 11 2017

Labels: -Merge-Request-58 Hotlist-Merge-Approved Merge-Approved-58
Your change meets the bar and is auto-approved for M58. Please go ahead and merge the CL to branch 3029 manually. Please contact milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), bhthompson@(cros), govind@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: pbomm...@chromium.org abdulsyed@chromium.org ranjitkan@chromium.org
M58 Merge: Please merge you change to M58 branch 3029 before 5:00 PM PT, Monday on so we can take it in for next week dev release. Thank you.

M57 Merge:
Re #14, Please note M57 stable is already out for small percentage of users, plan to ramp up AU to 5% in on Monday.If this change is important to merge to M57 for future stable release (if any) and safe to merge, please request a merge to M57 once change is well baked/verified in Canary/M58 Dev. Thank you.


Please merge your change to M58 branch 3029 before 5:00 PM PT, Monday (03/13/17) so we can take it in for next week dev release. Thank you!

Labels: Merge-Request-57
Is it too late to merge into M57?
Project Member

Comment 21 by sheriffbot@chromium.org, Mar 13 2017

Labels: -Merge-Request-57 Hotlist-Merge-Review Merge-Review-57
This bug requires manual review: Only 0 days from stable, we might already have a stable candidate build
Please contact the milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), ketakid@(cros), govind@(desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Merge-Review-57
Talked to govind@ offline and since this bug isn't critical, we should avoid merging it to M57
Labels: Needs-Feedback
Tested this issue on Mac 10.12.3 with chrome dev #58.0.3029.19

These are the steps followed
1. Launched chrome 
2. Disabled "Always show Toolbar in Full Screen"
3. Entered into fullscreen by typing "ctrl+cmd+F"
4. Opened few tabs using "Ctrl+T" cmd and observed that tab strip is appeared.
5. Moved the cursor somewhere and clicked on the page and observed that tab strip area 
   disappears

Attaching the screen-cast for reference.

spqchan@ could you confirm that this expected behavior of this fix.

Thank You...
Issue 689115.mp4
1.1 MB View Download
 Issue 701772  has been merged into this issue.
Status: Fixed (was: Started)
Yep, looks good thanks!
Cc: spqc...@chromium.org brajkumar@chromium.org
 Issue 693912  has been merged into this issue.
 Issue 703048  has been merged into this issue.
Labels: TE-Verified-M57 TE-Verified-57.0.2987.123
Rechecked the issue on Stable build 57.0.2987.123 on MAC 10.12.3 as per the steps provided in comment#23 and based on confirmation in comment#25, merge is working as intended. Adding TE-verified labels.

Sign in to add a comment