1197161 - Touch scrolling can affect the wrong scrollable div if there are more than one of them.

Status: RESOLVED FIXED

(Core :: Widget: Win32, defect)

Description

[mozillaid]

Attachment: Very simple HTML page consisting of two scrollable divs.

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36

Steps to reproduce:

1) On a Windows computer with a touchscreen (mine is a Surface Pro running Windows 10), open the attached very simple example test page, which contains two scrollable divs.

2) Touch one of the two divs, and wiggle your finger up and down.  Note that the div does indeed scroll.

3) Quickly move your finger from the first div to the other div, and then wiggle your finger up and down on that second div.  Your finger should leave the touchscreen when you move your finger between the two divs, but your finger has to be out of contact with the touchscreen for less than about one second.



Actual results:

The finger motion on the second div causes the first div to scroll.


Expected results:

The second div should scroll.

Comment 1

[mozillaid]

I just now also tested this on the current Developer version of Firefox (version 42), and it's still broken.

Edge and Chrome handle this correctly.

Comment 2

[Simona Badau, Desktop QA]

Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
BuildID: 20151221030239

I can confirm the issue is reproducible using the latest Nightly 46 on Microsoft Surface Pro 2 (Windows 10x64).
Setting to NEW.

Comment 3

[Jim Mathies [:jimm]]

This may not be a valid bug with apz.

Comment 4

[Botond Ballo [:botond]]

Confirmed - the problem no longer occurs when touch scrolling is driven by APZ.

Comment 5

[Kartikaya Gupta (email:[e-mail])]

Now that touch events are riding the trains I'm going to call this fixed in 52. Note that e10s still needs to be enabled in 52 to get proper touch events support.