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

Issue 645763 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Disable mouse cursor during 2-finger scroll

Project Member Reported by abodenha@chromium.org, Sep 10 2016

Issue description

From puneetster@:
We noticed that scrolling via touchpad was a lot more janky than via touchscreen.  It turns out there is a lot more work to be done in the touchpad version because the cursor enters and exits objects on the screen and the javasript helpers get fired as a result.  This doesn't happen for touch induced scroll because the cursor disappears during the scroll.

warx@ can you look into how the cursor disable is done on touch scroll and do something similar for 2-finger scroll?

If this ends up being simple we'll consider migration to 54.
 

Comment 1 by adlr@chromium.org, Sep 10 2016

I think we should hide the mouse cursor only when there is actual scrolling. For example, if you position the mouse over the tab strip and do 2-finger scrolling, the cursor should not hide.

If this works well on Kevin, we should really consider rolling out to all Chromebooks.
Why not hide immediately when we begin the scroll gesture? Trying to trigger based on what's under the mouse will add a lot of complexity and I'm not seeing the value.

I also REALLY don't want to special case this for Kevin. 
Re: comment #1 adlr@ I don't see how to trigger a scroll while having the cursor on a tabstrip.  Did you mean that the cursor should be hidden only if there is actual scrolling content to be scrolled?

Re: Comment #2 - I agree not to do something special for Kevin.  Hiding immediately when the scroll begins sounds right.  If there is no content to be scrolled nothing should happen.

Comment 4 by adlr@chromium.org, Sep 11 2016

We can try it out for any content being under the cursor. I was just thinking it may be jarring if you try to scroll and nothing happens and your cursor disappears.
Let's try hiding immediately on a scroll even regardless of content. If folks find it jarring, we can build something more complex.
Status: WontFix (was: Assigned)
Turns out there are already protections in place to prevent the cases this is trying to prevent.

Sign in to add a comment