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

Issue 648862 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Oct 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Regression:Scrolling and Scrollbar issue is observed on 'chrome://md-settings' if browser language is changed to 'Arabic'

Reported by dmascare...@etouch.net, Sep 21 2016

Issue description

Chrome Version:54.0.2840.34 (Official Build) dffe0812950a59945440dbdf19d836fd232c84d3-refs/branch-heads/2840@{#453}
OS: Windows (7,8,10)

Pre-condition: Change the browser language to 'Arabic'

What steps will reproduce the problem?
1. Launch chrome and navigate to chrome://md-settings/reset
2. Reload the page and click on Side nav menu,then click on 'Reset' option such that 'Reset' section is seen with padding below it.
3. Try to scroll via mousewheel and then drag the mouse upward & downward,observe scrollbar.

Actual:1. On scrolling via mousewheel, scrolling is too slow.  
       2. On dragging, scrollbar issue is observed [i.e. Down arrow button of scrollbar is not seen]. (refer screencast)

Expected:1. On scrolling via mousewheel, scrolling should be proper.
         2. On dragging, scrollbar should not proper [Down arrow should be seen]

This is regression issue,broken in 'M 54' and will soon update the bisect info:

Good build:54.0.2820.0
Bad build:54.0.2821.0

Note: Issue is not reproducible on Mac and Linus OS.

 
Actual_scroll.mp4
849 KB View Download
Correction in Manual Bisect info:

Good build: 54.0.2817.0
Bad build: 54.0.2819.0
Labels: hasbisect
Owner: dschuyler@chromium.org
Status: Assigned (was: Unconfirmed)
Narrow bisect:
https://chromium.googlesource.com/chromium/src/+log/97a8ae930e6e19506bf99b14d82ee4644cd7b29c..e9b7184afd9ac616fafe276f3172307538a2ff97?pretty=fuller&n=1000

Suspecting: r409669 

Kindly help to re-assign, if your changes are not cause for this issue.
Status: WontFix (was: Assigned)
I'm not able to reproduce this with the latest code.
I believe this may have been fixed by some recent CL(s).
Please let me know if the issue is still seen.

Sign in to add a comment