GitLab

Revert "Tab strip ideal bounds are calculated from the available width instead of the current width."

This reverts commit d091784a.

Reason for revert: caused crash regression https://bugs.chromium.org/p/chromium/issues/detail?id=1070980#c1

Original change's description:
> Tab strip ideal bounds are calculated from the available width instead of the current width.
> 
> This obviates the need for the work described in
> go/chrome-nonpredictive-tabstrip-animations.
> 
> One known issue: with stacked tabs enabled, resize a window to trigger
> a transition into the stacked layout. The tabs will animate into the
> new layout, and while this is taking place, they will ignore any
> further changes to the tabstrip's bounds.
> 
> Further work: Continue removing now-dead code from the new animation
> system.
> 
> Bug: 958173
> Change-Id: I977b3836ad87647fa17e431a1215ebd1ce81727c
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2055544
> Reviewed-by: Scott Violet <sky@chromium.org>
> Reviewed-by: Connie Wan <connily@chromium.org>
> Commit-Queue: Taylor Bergquist <tbergquist@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#759054}

TBR=sky@chromium.org,pbos@chromium.org,tbergquist@chromium.org,connily@chromium.org

Change-Id: I4b995aeb6515aa675442e4cf69a4a4d0be48e840
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 958173
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2151425Reviewed-by: Taylor Bergquist <tbergquist@chromium.org>
Commit-Queue: Taylor Bergquist <tbergquist@chromium.org>
Cr-Commit-Position: refs/heads/master@{#759374}