New issue
Advanced search Search tips

Issue 915765 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 864293
Owner: ----
Closed: Dec 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

overflow: scroll and css transform rendering bug

Reported by terrenpr...@gmail.com, Dec 17

Issue description

Steps to reproduce the problem:
Tap on "Trigger Bug" button.

Apply a transform to an overflow: scroll div that doesn't have enough content to scroll.

What is the expected behavior?
Nothing should happen.

What went wrong?
A strange dot appears at the top left of each scrollable div. This will disappear when you try to hover over it in DevTools. Tested on both Chrome for Android and Chrome for Windows with inspector open on "Responsive"/touch device. Results differ by device & if you add just overflow: scroll or specify different overflow-x and overflow-y (see demo).

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 73.0.3642.0  Channel: canary
OS Version: 8.0.0
Flash Version: 

For convenience, demo can also be found here: https://terpro.github.io/samples/scrollpixel.html
 
index.html
954 bytes View Download
android.jpg
25.0 KB View Download
windows.png
4.0 KB View Download
Components: Blink>Scroll
I suspect that this has something to do with the browser trying to render a scrollbar when it is not needed.
Labels: Needs-triage-Mobile
Cc: chelamcherla@chromium.org
Labels: Target-71 Target-72 Target-73 M-73 Triaged-Mobile FoundIn-71 FoundIn-72 FoundIn-73
Status: Untriaged (was: Unconfirmed)
Tested the issue in Android and able to reproduce the issue. 

Steps Followed:
1. Navigated to  https://terpro.github.io/samples/scrollpixel.html
2. Clicked on trigger bug and observed unwanted dot above content 1 and content 2.

Chrome versions tested:
73.0.3642.0 , 60.0.3072.0

OS:
Android 9.0.0

Android Devices:
Pixel XL

Issue is seen in from older M-60 builds, hence considering this issue as Non-Regression and marking as Untriaged for further inputs from dev team.

Please navigate to below link for log's  --
go/chrome-androidlogs/915765

Thanks!
Cc: bokan@chromium.org
Status: Available (was: Untriaged)
Maybe similar to issue 864293?

Comment 6 Deleted

Yes, this looks like the same problem. Fortunately I have isolated the issue so it should be easier to investigate. I have also determined that this is not a mobile-only issue.
Mergedinto: 864293
Status: Duplicate (was: Available)
Thanks! The reduced case should make this easier to debug.

Sign in to add a comment