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

Issue 665117 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
inactive
Closed: Jan 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug

Blocking:
issue 665124



Sign in to add a comment

Background color flicker after warming up CCTs

Project Member Reported by aelias@chromium.org, Nov 14 2016

Issue description

Originally posted in http://crbug.com/653249#c11

1. Open any webpage in a regular Chrome tab.
2. Using the AGSA Google app, search for a query and click on one of the search results to launch a custom tab.
3. Using the custom tabs client example app, "warmup" and "may launch" any url and then launch a custom tab.
4. Switch between the custom tabs or the Chrome tab via Recents.

Observed behavior:
The content in the custom tab flickers.

Expected behavior:
The content in the custom tab should not flash/flicker.

Important Notes:
- This seems to happen more reliably if "warmup" and "may launch" are called before launching the custom tab. For e.g, in repro step 3 above, if the tab is launched without "warmup" and "may launch", I wasn't able to repro the flickering consistently.
- I have added a video showing current behavior here: http://go/chrome-androidlogs1/6/653249 (Ignore the artifacts at the bottom of the video, but that seems to be a problem with screenrecord)

Device: Pixel XL / NMF26D
 

Comment 1 by aelias@chromium.org, Nov 14 2016

Blocking: 665124

Comment 2 by aelias@chromium.org, Jan 27 2017

Cc: jay...@chromium.org
Status: Fixed (was: Assigned)
Can no longer repro on 55.0.2883.91/Nexus 6P/NMF26F.  Note GSA links don't open in CCT for me (open directly in Chrome instead) so I tried to reproduce with two different copies of CCT example client app instead.  I think one of the fixes may have affected this.  jayker@, please verify or reopen.

Comment 3 by jay...@chromium.org, Jan 28 2017

Status: Verified (was: Fixed)
I no longer see the flashes, with the steps in the bug description, on a Pixel XL / NMF26D and Chrome 55.0.2883.91

AGSA sometimes needs the custom tabs integration to be "synced", by going to AGSA settings -> Accounts & Privacy. If the "Open in web pages in app" switch is toggled to on, that should be enough to get custom tabs to launch.

Sign in to add a comment