New issue
Advanced search Search tips

Issue 882406 link

Starred by 2 users
Status: Verified
Owner: ----
Closed: Sep 11
Cc:
chelamcherla@chromium.org
bokan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Multiple unresponsible pages after last Canary update

Project Member Reported by mar...@mwiacek.com, Sep 10 
Device name:s7

From "Settings > About Chrome"
Application version:71.0.3548.0
Operating system:8.0

URLs (if applicable):tvnwarszawa.pl

Steps to reproduce:
(1)open url

Expected result:
page can be nice scrolled

Actual result:
ugly performance + some scroll gestures are visible like long press normally used for opening context menu.

previous Canary - OK; stable - OK

Comment 1 by mar...@mwiacek.com, Sep 10

Summary: Unresponsible many pages after last Canary update (was: Unresponsible page after last Canary update)

Comment 2 by mar...@mwiacek.com, Sep 10 

Visible of various URLs, for example innpoland.pl.

Comment 3 by mar...@mwiacek.com, Sep 10

Summary: Multiple unresponsible pages after last Canary update (was: Unresponsible many pages after last Canary update)

Comment 4 by bokan@chromium.org, Sep 10

Cc: bokan@chromium.org
Components: -Internals>Mobile>Web -Blink Blink>Scroll
marcin@, could you please capture and attach a trace using these instructions: https://www.chromium.org/developers/how-tos/submitting-a-performance-bug

Comment 5 by mar...@mwiacek.com, Sep 10 

maybe tomorrow I will be able

...but it shouldn't be difficult for SWE to track it - the same I observed with Pixel with Android P.

Comment 6 by chelamcherla@chromium.org, Sep 11

Labels: Needs-triage-Mobile

Comment 7 by chelamcherla@chromium.org, Sep 11

Cc: chelamcherla@chromium.org
Labels: Triaged-Mobile Needs-Feedback
Tested the issue on Samsung s7 using latest canary 71.0.3548.0 and on scrolling no lag is seen and smooth scrolling is seen.

As per C#4 and c#5 adding Needs-Feedback label.

Thanks!

Comment 8 by bokan@chromium.org, Sep 11

Status: Closed (was: Unconfirmed)
I can repro the issue on 71.0.3548.0 but not on 71.0.3549.0 so it looks like this got fixed elsewhere. I'm going to close the issue but feel free to reply if you're still seeing it and we can take another look.

Comment 9 by mar...@mwiacek.com, Sep 11

Status: Verified (was: Closed)
I confirm, thx.
►

Sign in to add a comment