Can't “grab” custom Chrome scrollbar with mobile
Reported by
terrence...@gmail.com,
May 11 2016
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36 Example URL: https://jsfiddle.net/dr8g4g6k/2/ Steps to reproduce the problem: 1. Follow the JS fiddle provided 2. Switch Chrome to mobile emulation, any device 3. Try to "grab" the scrollbar to scroll What is the expected behavior? You should be able to grab and scroll it just like the regular Chrome scrollbar What went wrong? You can't get to it at all Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes v30 Does this work in other browsers? Yes Chrome version: 50.0.2661.94 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 21.0 r0 I've entered a stackoverflow as well: http://stackoverflow.com/questions/37173163/cant-grab-custom-chrome-scrollbar-with-mobile
,
May 12 2016
Do you mean "toggle device mode" in the devtools by "mobile emulation"?
,
May 12 2016
Yes, the button next to select element in dev tools which let's you change between different devices and also uses touch events instead of mouse events (touchstart instead of click). You can also just use an Android device. I have a Nexus 6P and its the same on it. But since I can also replicate on desktop Chrome while using this device mode, I know it's something in Chrome.
,
May 12 2016
,
May 12 2016
I believe this is an aspect of how touch simulation works from Devtools. You are able to drag it the first time the page is transitioned from opening devtools but if you refresh it you can no longer drag the scrollbar. Dmitry any idea?
,
May 12 2016
Thank you for your reply. When you refresh, it then properly sends touch commands instead. But please remember I am also able to replicate this on my Nexus 6P device (and Galaxy S3), so I think the only time it ever works is when you first enable "device mode" because at that time, it's still somehow getting a click (I presume).
,
May 12 2016
Chrome does not allow to grab the main frame scrollbar on Android (and thus in mobile emulation mode). skobes@, am I right here? Unfortunately, to get full Android-like behavior with scrollbars, you have to reload after enabling mobile emulation. That's a limitation we were not able to get rid of.
,
May 12 2016
@Comment 7 You are able to 'grab' the Android scrollbar if you first start to scroll. After it shows up, while it's there (for a few seconds), you can indeed grab it. So I feel it should be allowed for custom ones as well, especially since all my content (in my case) is doing lasso selection (and thus, cannot pan). As such, for my mobile application, I am relying on the scrollbar.
,
May 12 2016
Hmm, it seems to me that *no* scrollbars are draggable on real Android, but some scrollbars are draggable in mobile emulation mode. I'm not sure if there was a product decision to make them undraggable, or if that's a bug. Maybe aelias can shed some insight. I think native Android scrollbars are too thin to work well as drag targets, but we could possibly make an exception for custom scrollbars. Regardless, we should make mobile emulation mode match the real thing as much as possible.
,
May 12 2016
skobes@ as per comment #7 this seems to be what it is doing. You need to reload to get the full android like behavior. I'm guessing this issue can just be closed as working as intended?
,
May 12 2016
Custom scrollbars are a webkit-prefixed misfeature I'd like us to eventually deprecate and remove anyway. They don't provide any capabilities you can't achieve with normal HTML/CSS/JS, so the only valid use case for them from my POV is to remove the scrollbar entirely.
,
May 12 2016
@10: Even after reloading, some scrollbars are draggable in mobile emulation mode. But I guess that's tangential. It sounds like Android scrollbars aren't meant to be draggable, and we don't want to add exceptions for custom scrollbars, so this bug is WontFix. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by terrence...@gmail.com
, May 11 2016