New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 853879 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jun 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug

Blocking:
issue 831359



Sign in to add a comment

Blank tabs in Android horizontal tab switcher during scrolling

Project Member Reported by rlanday@chromium.org, Jun 18 2018

Issue description

Tabs are blank during quick scrolling
 
Project Member

Comment 2 by sheriffbot@chromium.org, Jun 18 2018

Labels: -Merge-Request-68 Hotlist-Merge-Review Merge-Review-68
This bug requires manual review: M68 has already been promoted to the beta branch, so this requires manual review
Please contact the milestone owner if you have questions.
Owners: cmasso@(Android), kariahda@(iOS), bhthompson@(ChromeOS), abdulsyed@(Desktop)

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

Comment 3 by bugdroid1@chromium.org, Jun 18 2018

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a272f89037041cbfb4fae2a4456e68052c6b287c

commit a272f89037041cbfb4fae2a4456e68052c6b287c
Author: Ryan Landay <rlanday@chromium.org>
Date: Mon Jun 18 22:37:12 2018

Fix blank tabs during scrolling in Android horizontal tab switcher

In the Android horizontal tab switcher, we determine which tab thumbnails to
render based on the index of the currently-centered tab, as determined by
NonOverlappingStack#computeReferenceIndex() (this is a virtual method called by
Stack since the logic for updating visibility is shared between the overlapping
and non-overlapping tab switchers). We currently have a bug where the tab
thumbnails are becoming blank during quick scrolling. This is because the
current implementation of this method uses mScrollTarget instead of
mScrollOffset to determine the centered tab (basically, mScrollTarget is where
we're going and mScrollOffset is where we are, and is actually used for
rendering).

This CL fixes this bug by updating this method's implementation to use the value
returned from getCenteredTabIndex(), which uses mScrollOffset instead of
mScrollTarget.

Bug:  853879 ,831359
Change-Id: I129c03ca80297c15b670d223bfc6630b6d8de68c
Reviewed-on: https://chromium-review.googlesource.com/1105021
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Ryan Landay <rlanday@chromium.org>
Cr-Commit-Position: refs/heads/master@{#568203}
[modify] https://crrev.com/a272f89037041cbfb4fae2a4456e68052c6b287c/chrome/android/java/src/org/chromium/chrome/browser/compositor/layouts/phone/stack/NonOverlappingStack.java

Comment 4 by cma...@chromium.org, Jun 19 2018

Labels: -Hotlist-Merge-Review -Merge-Review-68 Merge-Approved-68
Status: Fixed (was: Started)
Project Member

Comment 6 by bugdroid1@chromium.org, Jun 21 2018

Labels: -merge-approved-68 merge-merged-3440
The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/40c80d392aca9d9f282550c6e2f603942b589e97

commit 40c80d392aca9d9f282550c6e2f603942b589e97
Author: Ryan Landay <rlanday@chromium.org>
Date: Thu Jun 21 16:09:40 2018

Fix blank tabs during scrolling in Android horizontal tab switcher

In the Android horizontal tab switcher, we determine which tab thumbnails to
render based on the index of the currently-centered tab, as determined by
NonOverlappingStack#computeReferenceIndex() (this is a virtual method called by
Stack since the logic for updating visibility is shared between the overlapping
and non-overlapping tab switchers). We currently have a bug where the tab
thumbnails are becoming blank during quick scrolling. This is because the
current implementation of this method uses mScrollTarget instead of
mScrollOffset to determine the centered tab (basically, mScrollTarget is where
we're going and mScrollOffset is where we are, and is actually used for
rendering).

This CL fixes this bug by updating this method's implementation to use the value
returned from getCenteredTabIndex(), which uses mScrollOffset instead of
mScrollTarget.

Bug:  853879 ,831359
Change-Id: I129c03ca80297c15b670d223bfc6630b6d8de68c
Reviewed-on: https://chromium-review.googlesource.com/1105021
Reviewed-by: Matthew Jones <mdjones@chromium.org>
Commit-Queue: Ryan Landay <rlanday@chromium.org>
Cr-Original-Commit-Position: refs/heads/master@{#568203}(cherry picked from commit a272f89037041cbfb4fae2a4456e68052c6b287c)
Reviewed-on: https://chromium-review.googlesource.com/1110277
Reviewed-by: Ryan Landay <rlanday@chromium.org>
Cr-Commit-Position: refs/branch-heads/3440@{#472}
Cr-Branched-From: 010ddcfda246975d194964ccf20038ebbdec6084-refs/heads/master@{#561733}
[modify] https://crrev.com/40c80d392aca9d9f282550c6e2f603942b589e97/chrome/android/java/src/org/chromium/chrome/browser/compositor/layouts/phone/stack/NonOverlappingStack.java

Status: Verified (was: Fixed)
Didn't see any blank issues while scrolling.
Tested on: Sony Xperia M4 Aqua (E2306) / 6.0.1

Sign in to add a comment