TabGroup index changed during restoration process |
|||
Issue descriptionAfter tab restoration at cold start, The TabGroupList will be re-ordered in tab switcher if the last shown tab before Chrome is killed is in group index > 1 while the TabModel retains the old tab ordering. This cause toolbar switch tab incorrectly. The last shown tab before Chrome is killed will be restored first and added the TabModel during the ChromeTabbedActivity#initializeState(). Then TabGroupList is created and initialized from TabModel during ChromeTabbedActivity#initializeUI() called which other tabs has not been restored yet.
,
Oct 11
,
Oct 11
Right now the ordering of tab groups is not kept after restarting, and the tab ordering within a tab group isn't either. We might be able to rely on the tab indexes inside TabModel to help the ordering in TabGroupList.
,
Oct 22
The ordering of tabs is inconsistent between the tab group/strip and the TabModel, which is used by swiping left and right on the toolbar.
,
Nov 6
|
|||
►
Sign in to add a comment |
|||
Comment 1 by meili...@chromium.org
, Sep 6