New issue
Advanced search Search tips

Issue 604699 link

Starred by 2 users

Issue metadata

Status: Archived
Owner:
Closed: Aug 14
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Weird traces of scroll bar appears on image section for 'HUMAN 3.0' app.

Reported by dchau...@etouch.net, Apr 19 2016

Issue description

Chrome Version: 51.0.2704.19 (Official Build) 0add88a3aa2b8ecc95df9dd721dd5b05571e7a5b-refs/branch-heads/2704@{#121} 32/64-bit.
OS: Windows(Win 7-Aero enabled), Linux.

URL: https://chrome.google.com/webstore/detail/human-30/meefjekipolcgabfgaclcpdkbghhmoah/related?utm_source=chrome-ntp-icon

What steps will reproduce the problem?
1. Launch chrome, login to chrome with valid credentials, go to above URL and add it.
2. Launch the 'HUMAN 3.0' app from chrome//apps and click on "</>" (Embed) icon.
3. Drag the 'H' slider to extreme right (scroll bar appears) and then drag it to extreme left and observe.

Traces of scroll bar appears on image section.
Traces of scroll bar should not appear on image section.

This is a regression issue, broken in M-51 series, below is bisect info.

Manual regression range:

Good build: 51.0.2695.0
Bad build: 51.0.2696.0

Narrow bisect:
https://chromium.googlesource.com/chromium/src/+log/8694d7b928ba2b7bfe73fbcb74d052faa5eb309c..4c9fd0d3128c87e1289e9ac1d47fec18d7107077?pretty=fuller&n=100

Suspecting: r384377 ?

@sky: Kindly help to reassign if your changes are not related to this issue.

Note: This issue is not seen on Mac OS.

Kindly review the attached screen-cast for reference.
 
Traces_Screenshot.png
361 KB View Download
Actual_behavior.mp4
1.9 MB Download
Expected_behavior.mp4
644 KB Download
Status: Archived (was: Assigned)
Archiving old bugs that haven't been modified in over two years. 

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!
Archiving old bugs that haven't been modified in over two years. 

If you feel this issue should still be addressed, feel free to reopen it or to file a new issue. Thanks!

Sign in to add a comment