Issue metadata
Sign in to add a comment
|
Regression: Unwanted extra space is seen between + icon and tabstrip after resizing browser window.
Reported by
db...@etouch.net,
Nov 21
|
||||||||||||||||||||||
Issue descriptionChrome Version: 72.0.3617.0 Revision 4b5e988589e5f4f1db23c9441c7739ca6f1bd72b-refs/branch-heads/3617@{#1}(32/64 bit) OS: Windows(7,8,8.1,10) What steps will reproduce the problem? (1) Launch chrome, open multiple tabs then resize browser window. (2) Observe space between + icon and tabstrip. Actual: Unwanted extra space is seen between + icon and tabstrip. Expected: No such a extra space should seen. This is a regression issue, broken in 'M69', will soon update the other info: Good Build:69.0.3476.0 Bad Build: 69.0.3478.0 Note: issue is not seen on Mac(10.13.1,10.13.6,10.14.6) and Linux(10.14LTS) OS.
,
Nov 22
,
Nov 22
,
Nov 29
,
Dec 11
,
Dec 13
This is actually longstanding behavior of being in overflow -- the new tab button pins to the right edge of the max width of the tabstrip, even if we can't divide that into the existing tabs evenly. We could reflow tabs to take up the space or move the new tab button to the left to pin to the rightmost visible tab; the latter would probably be better, but it still means that there'd be a movement jump of unpredictable size between "full tabstrip" and "overflowing tabstrip". This seems worse than leaving the gap. This will be moot with scrolling tabs anyway, so closing. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by db...@etouch.net
, Nov 21Labels: hasbisect
Owner: pkasting@chromium.org
Status: Assigned (was: Unconfirmed)