New issue
Advanced search Search tips

Issue 897989 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 16
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression: If many tabs open, latest tabs are not shown. Tab bar UI space is wasted unnecessarily.

Reported by reanimat...@gmail.com, Oct 23

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.67 Safari/537.36

Steps to reproduce the problem:
1. Open a new browser window.
2. Resize the window to be somewhat small.
3. Click new tab continually until you notice that no tabs appear selected. This is because the tab bar ran out of space to display tabs, and thus the currently-selected tab has been created in an x position beyond the right side of the window and is now occluded. This should not be the case. All tabs should scoot left such that the leftmost tabs are be occluded instead.
4. Separately, notice that when the tab bar is "full", there is about 2 tabs worth of unused space to the right of the "new tab" button. This should be utilized rather than being wasted space, as shown in the 2nd attached screenshot.

What is the expected behavior?
The user's current tab should ALWAYS be shown, even if the tab bar is completely full. Other browsers handle this by scooting the oldest/leftmost tabs offscreen to the left as new tabs are opened. Some have arrows that appear allowing you to horizontally scroll to see the occluded tabs.

Additionally, as shown in the attached screenshot, the tab bar should 

What went wrong?
Chrome simply adds additional tabs to the right of the tab bar until the currently selected tab can no longer be seen, even if while still shown in the main window area. There is therefore no way to close the tab, drag it to a new window, etc.

Did this work before? Yes 69.x

Chrome version: 72.0.3588.0 (Official Build) canary (64-bit)  Channel: canary
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: n/a

There is a related occlusion issue with the speaker icon sound indicator for sound-playing tabs. It would be nice if tabs which are playing sound would still show the speaker indicator somehow, even if there is not room on the tab for both the speaker icon and the favicon. (They are currently placed adjacent to each other - perhaps alternate between the two in a single icon position if there is not room for both icons?)

Rationale: The sound indicator is most useful when there are more tabs open than would be reasonable to flip through to find which one is playing sound. This is a feature built to assist with an issue that arises often when having many tabs open, but yet beyond a certain number of tabs, it's no longer visible at all, rendering it useless. My proposed suggestion would allow for at least 2x as many tabs to be shown before the icon loses its' usefulness (in which case, even the favicon would have been occluded entirely).
 
chrometabs1.png
42.8 KB View Download
chrometabs2.png
19.2 KB View Download
Labels: Needs-Bisect Needs-Triage-M72
Cc: viswa.karala@chromium.org
Labels: Triaged-ET Needs-Feedback
Tested the issue on chrome reported version# 72.0.3588.0 using Windows-10 with steps mentioned below:
1) Launched chrome reported version and opened multiple tabs until no tabs appear selected
2) When multiple tabs are selected compared the behavior(space between last tab and '+' button) of '+' button, seen same behavior when compared with 69.0.3497.100(find attached for the same).

@Reporter: Please find the attached screenshots for your reference and let us know if we missed anything in reproducing the issue, provide your feedback on it which help in further triaging it in better way.

Thanks!
897989 - 72.0.3588.0.PNG
83.1 KB View Download
897989 - 69.0.3497.100.PNG
68.5 KB View Download
Cc: vamshi.kommuri@chromium.org
 Issue 897948  has been merged into this issue.
Labels: Hotlist-DesktopUIChecked
Status: WontFix (was: Unconfirmed)
*** UI Mass Triage ***

We were unable to reproduce this bug. If this bug still reproduces for you, 
please reopen or file a new issue. Thanks!

Sign in to add a comment