New issue
Advanced search Search tips

Issue 590641 link

Starred by 2 users

Issue metadata

Status: Archived
Owner: ----
Closed: Sep 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Tab row disappears entirely when total pinned tab width exceeds window width

Reported by aever...@gmail.com, Feb 29 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2662.0 Safari/537.36

Steps to reproduce the problem:
1. Open a new browser window (⌘N).
2. Open a few tabs and right-click and pin them.
3. Resize your browser window horizontally so that the window's width is narrower than the total width of all pinned tabs.

Observe that all browser tabs in the window disappear until the window is resized to be wider than the pinned tabs.

What is the expected behavior?
Anything besides all the tabs disappearing would be a better user experience.

What went wrong?
Browser tabs disappeared. See screenshot.

Did this work before? N/A 

Chrome version: 51.0.2662.0  Channel: n/a
OS Version: OS X 10.11.4
Flash Version: Shockwave Flash 21.0 r0
 
bye-bye-tabs.png
106 KB View Download
Components: -UI UI>Browser>TabStrip
Labels: -Type-Bug Needs-Bisect Type-Bug-Regression
This sounds like a regression. 

Comment 2 by ajha@chromium.org, Mar 2 2016

Cc: ajha@chromium.org
Labels: -Pri-2 -Needs-Bisect M-51 hasbisect Pri-1
Owner: andresantoso@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this on the latest canary(51.0.2665.0) and the latest stable(48.0.2564.116) on Mac OS 10.11.3 and this worked fine on Windows-7 and Linux Ubuntu 14.04 with the same chrome versions.

Test steps:
===========
1. Opened 8 new tabs and pinned all of them.
2. Resized the browser horizontally such that the width of the window is less than pinned tabs and observe.

Observed: All the pinned tabs disappear.

This has regressed in M-39.

Last good build: 39.0.2149.0
First bad build: 39.0.2150.0

Change log:
============
https://chromium.googlesource.com/chromium/src/+log/39.0.2149.0..39.0.2150.0?pretty=fuller&n=10000

On manual inspection suspecting: https://codereview.chromium.org/476313003

andresantoso@: Could you please take a look at this.

Thank you!
Owner: pinkerton@chromium.org
Cc: pinkerton@chromium.org
Labels: -Pri-1 -M-51 M-52 Pri-2
Owner: shrike@chromium.org
Heh. Cute. -> shrike for a look.

Regressed in M39? Hardly a requirement for M51. Downgrading priority. 
Project Member

Comment 5 by sheriffbot@chromium.org, Jun 1 2016

Labels: -M-52 M-53 MovedFrom-52
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 6 by sheriffbot@chromium.org, Jul 15 2016

Labels: -M-53 MovedFrom-53
This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 7 by shrike@chromium.org, Jan 25 2018

Labels: Hotlist-PlatformExcellence
Owner: ----
Status: Available (was: Assigned)
Status: Archived (was: Available)
Archiving old bugs that haven't been actively assigned in over 180 days.

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
This is fixed in Chrome 69 (69.0.3497.100) on macOS. The new tab row design did the trick.

Sign in to add a comment