1460640 - [aarch64] First mouse drag after touch dragging tab is ignored

Status: NEW

(Core :: Widget: Win32, defect, P3)

Description

[Adam Gashlin (he/him) [:agashlin] (ex-moco)]

Since the fix for bug 1457338 went in, touch dragging a tab will cause the next mouse drag (of tabs or otherwise) to be ignored (not always, though I'm not sure what the difference is, and not if you click the mouse first).

Observed on a Dell XPS 15-inch (2017) (aka XPS 15 9560 Signature Edition).

After the first mouse drag things seem to go back to normal, but there is also the odd issue with text selections in bug 1460637, which may be related.

Comment 1

[Daniel Bodea [:danibodea]]

I cannot reproduce this issue or I do not fully understand it.
Could you, please, retry it's reproduction?

If it still reproduces, please write some detailed and unambiguous steps to reproduce with actual and expected results.

Thank you for your contribution!

Comment 2

[Adam Gashlin (he/him) [:agashlin] (ex-moco)]

Attachment: demonstration

Steps to reproduce:

1. Open a current nightly with a fresh profile. This should have two tabs.
2. Tap with the touchscreen on the non-active tab. (Touch-dragging tabs does not seem to work at all until after you've done this, which seems to be a new bug)
3. Touch drag the tab so that it moves in the tab bar.
4. Click and drag the tab with the mouse.

Expected result:
The tab moves when dragged with the mouse

Actual result:
The tab does not move. It will move if you try dragging it a second time, though.

In the attached video, after I drag the tab with the touchscreen, I try to drag it with the touchpad/mouse twice, the first time has no effect.

Comment 3

[Daniel Bodea [:danibodea]]

I can confirm the reproduction in the video on Nightly v67.0a1 (2019-02-11) (64-bit) (target: aarch64-windows-mingw32)
It does not occur on the generic (non-aarch64) 32-bit build, Nightly v67.0a1 (2019-02-11) (32-bit) (target: i686-pc-mingw32)

Confirmed on Lenovo Yoga C630-13Q50 with Windows 10 Home (v1803).