New issue
Advanced search Search tips

Issue 677366 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

history buttons get stuck

Reported by pdk...@gmail.com, Dec 29 2016

Issue description

Steps to reproduce the problem:
What happens is that tapping and releasing the back button doesn't return the button to default state. It remains as if it where still tapped. The only way to clear the state is to repaint that section, by scrolling down and thus hiding the chrome.

It happens intermittently, and appears to be more likely to occur after user input via keyboard, but that could be a coincidence. I haven't noticed a clear pattern yet.

What is the expected behavior?

What went wrong?
^

Did this work before? Yes 

Chrome version: 56.0.2924.18  Channel: beta
OS Version: M
Flash Version:
 
Cc: dknandiraju@chromium.org
Labels: triage-te

Comment 2 Deleted

Labels: Needs-Feedback
@pdknsk@gmail.com, can you please provide device details if possible

Comment 4 by pdk...@gmail.com, Feb 5 2017

I've recorded a video in which I alternately click both buttons, and scroll to clear  buttons.

The problem is apparently that the animation doesn't complete. Note there are some additional oddities. Sometimes there is no visual indication (on default button states) when a button is clicked, and the video ends with a correct button animation.

bug.webm
1.9 MB View Download
Labels: -Needs-Feedback
Owner: tedc...@chromium.org
Status: Assigned (was: Unconfirmed)
@tedchoc, could you please look into this issue. 

Note:
Please find logs and screen record taken on Samsung Galaxy TabS2(SM-T815Y)/MMB29K@ http://go/chrome-androidlogs1/6/677366

Comment 6 by pdk...@gmail.com, Feb 8 2017

This also affects other buttons, such as the up/down arrows in page search.
Cc: tedc...@chromium.org
Owner: mdjones@chromium.org
@mdjones, does our CompositorViewHolder touch handling ever get executed for the tablet toolbar?  I'm wondering if we're not giving the full event stream to the views so the drawables aren't getting the necessary signals to finish their animations.
Issue 576814 has been merged into this issue.
Yes, but we removed a good amount of the manual touch event routing that would likely be the culprit here. In fact, the CompositorViewHolder is now a sibling of the control container and the last to be offered touch events, so I would expect that the button is getting an up event. I'll take a closer look when I get some time.
Labels: -triage-te

Comment 11 by pdk...@gmail.com, Aug 1 2017

Still in M60, albeit somewhat different. More often than not no animation is played, or the animation stops late, when the rectangle is fully painted, rather than early.

Comment 12 by pdk...@gmail.com, Nov 20 2017

Still in M63.

Sign in to add a comment