Issue metadata
Sign in to add a comment
|
Regression: Flickering is seen on scrolling in hangouts app |
||||||||||||||||||||||||
Issue descriptionVersion: 53.0.2746.0/8369.0.0 (Official Build) dev-channel daisy, Peppy OS: Chrome Test URL:https://chrome.google.com/webstore/detail/google-hangouts/knipolnnllmklapflnccelgolnpehhpl?utm_source=chrome-app-launcher-info-dialog What steps will reproduce the problem? (1) Sign in to user and add above app (2) Now scroll the page by click and drag and observe Expected: No flickering should be seen on scrolling Actual: Instead flickering is seen. This is a Regression issue as issue is not seen in M50: 50.0.2661.103/7978.74.0 stable-channel Daisy @skobes: Please confirm the issue.
,
May 25 2016
Able to reproduce the issue on peppy using chrome version 53.0.2746.0/8369.0.0
,
May 25 2016
Issue is also seen in 52.0.2743.0/8350.3.0 (Official Build) dev-channel peppy. Flickering is also seen in Add new services of Files app. @bsep: Please help in re-assigning if it not related to your change.
,
Jun 3 2016
Issue is still seen in 53.0.2754.0/8405.0.0 (Official Build) dev-channel parrot,peach-pit,Jerry. NOTE: Issue is also seen on scrolling any pdf page with two fingers[Click and drag the scrollbar]. Attaching screen cast of same.
,
Jun 6 2016
This doesn't repro on Windows so I can't determine if this is related to my change or not. Re-assigning to someone who can help...
,
Jun 6 2016
I was unable to reproduce this on 53.0.2759.0 veyron_minnie (Flip) kavvaru@, can you test this on latest canary? I wonder if this is OOPIF related issue. +wjmaclean@, nasko@
,
Jun 6 2016
If it is OOPIF related, the client will be in the isolated extensions experiment. Can you check for it in chrome://version/? It should be under Variations with value of 69bf80fa-3f4a17df if enabled.
,
Jun 6 2016
I also missed the detail that it repros on stable, which is unlikely to be OOPIF, as those are only possible on Dev channel.
,
Jun 6 2016
Both reports (#0, and #4) are on dev channel. My minnie was canary and that may be why it didn't happen? (chrome://version does not have that value) Is it possible to manually enable it?
,
Jun 6 2016
The experiment name is encoded as 69bf80fa, so it should have at least that if it is on Dev. If the value after the dash is f23d1dea, then it is disabled. Enabling can be done through the command line either by adding --isolate-extensions or --force-fieldtrials=SiteIsolationExtensions/Enabled.
,
Jun 6 2016
I think oopif is unrelated. I tested with above flag and I could not reproduce this. However, I could reproduce this on samus (52.0.2743.19 dev), which does not have this experiment. kavvaru@, please test on the latest image. If this has been fixed on ToT, we can bisect when it was fixed at least.
,
Jun 7 2016
We are lucky. The Chrome OS bisect range matches just 1 Chrome version change: 8415.0.0 53.0.2758.0 NG 8417.0.0 53.0.2759.0 OK
,
Jun 7 2016
The issue was fixed on ToT by this patch: https://codereview.chromium.org/2015373002 """ Fix webview crash on attempt to scroll. This fixes crash of webview when its content is scrolled using 2-fingers gesture via touchpad or using touchscreen. """ This patch was fixing issue 615512 .
,
Jun 7 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sc00335...@techmahindra.com
, May 25 2016840 KB
840 KB Download