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

Issue 898811 link

Starred by 4 users
Status: Available
Owner: ----
Cc:
yyushkina@chromium.org
nyerramilli@chromium.org
rbasuvula@chromium.org
█ ramyan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows , Mac
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression:[NTP]Scroll doesn't work properly for 'Select a collection' overlay on press + hold of down arrow key

Reported by vineetha...@etouch.net, Oct 25 
Chrome Version: 72.0.3590.0 (Official Build)Revision ec242826af28a2b3c3b47390ab6141cfe26fe9e7-refs/branch-heads/3590@{#1}(32/64-Bit)
OS: Windows(7,8,8.1,10), Mac (10.13.1, 10.13.6, 10.14.1)

Steps to reproduce:
1.Launch chrome and navigate to chrome://flags, click on 'Reset all to default' and relaunch browser.
2.Open NTP and click on gear icon then select 'Choose background' option,observe 'Select a collection' overlay is seen.
3.Choose any tile under 'Select a collection' and then choose any wallpaper.
4.Now continuously press down arrow key and release after few scrolls and Observe.

Actual Result  : Pressing and holding down Arrow key causes wallpaper page to scroll back to original position.               
Expected Result: Scroll position should be seen on wallpaper where Down Arrow key was released.
                 
This is a regression issue, broken in 'M-70', and below is the bisect info:
Good Build:70.0.3537.0 (Revision: 587303)
Bad Build :71.0.3538.0 (Revision: 587811)

Change-Log URL: https://chromium.googlesource.com/chromium/src/+log/70.0.3537.0..70.0.3538.0?pretty=fuller&n=10000 

Suspecting:r587382?

@sweilun: Pardon me if this is an intended change. Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Note:
1. Providing suspect through 'Change-Log' because unable to perform bisect using 'per-revision' and 'chromium bisect' script.
2. Tried performing 'per revision' bisect on multiple Windows, Mac machines but unable to perform the same since getting "RuntimeError: We don't have enough builds to bisect" error .
3. Unable to perform 'chromium bisect' script as issue is not reproducible on chromium builds. 
4. This is an issue with remote NTP.

Thank you
ActualVideo.mp4
3.0 MB View Download
ExpectedVideo.mp4
978 KB View Download

Comment 1 by rbasuvula@chromium.org, Oct 25

Labels: ReleaseBlock-Stable
Adding release blocker label for this issue.Please reduce priority or remove if not the case.

Thank You!

Comment 2 by manoranj...@chromium.org, Oct 25

Owner: vineetha...@etouch.net
vineetha.sarma@, thank you for the report. Can you please test this on latest canary# 72.0.3591.0 and update the results?

Comment 3 by ramyan@chromium.org, Oct 25

Cc: yyushkina@chromium.org
Labels: -Pri-1 -ReleaseBlock-Stable -Target-70 -Target-71 Pri-2
This appears to be a remote NTP issue, and should not be a release blocker for any Chromium release. AFAICT, it's not reproducible on local NTP for M70, M71 or M72 - please do confirm with your findings vineetha.sarma@. 

Given this and the relative severity of the issue, I'm updating the attached labels to slot this appropriately into our queue. Thanks!

Comment 4 by vineetha...@etouch.net, Oct 26

Owner: sweilun@chromium.org
Update w.r.t. comment #3,

The above issue is reproducible on latest Canary build #72.0.3592.0 only on remote NTP. Kindly refer attached screen cast.

Thank you
CanaryBehaviour.mp4
2.1 MB View Download

Comment 5 by ramyan@chromium.org, Oct 26

Labels: AddToRemoteNTP
Owner: ----
Status: Available (was: Assigned)
vineetha.sarma@: Thanks for the confirmation! 

I'm leaving this available as sweilun@ has other priorities right now.

Comment 6 by twelling...@chromium.org, Oct 30

Labels: zine-triaged
►

Sign in to add a comment