1523998 - Google Maps pinch zoom on Windows touchscreen is "jumpier" than Edge

Status: RESOLVED WORKSFORME

(Core :: DOM: Events, defect, P2)

Description

[Andrew Overholt [:overholt]]

I made a video showing the issue. I don't know how to describe it :)

https://www.dropbox.com/s/4rvol4114x2lu6h/1080p.mov?dl=0

Comment 1

[Olli Pettay [:smaug][[e-mail]]]

My guess is https://bugzilla.mozilla.org/show_bug.cgi?id=1502529 affects this.

I was thinking about the same one.

Comment 2

[Edgar Chen [:edgar]]

I also experienced this and could not reproduce after switching pointer event off.

Comment 3

[Edgar Chen [:edgar]]

I quickly ran a trial build including a fix of bug 1323400, it seems it also help this issue.

Comment 5

[Timea Cernea [:tbabos][inactive]]

Reproduced on Lenovo Yoga C630-13Q50 with Windows 10 Home (v1803) on latest Nightly aarch64 build.

Comment 6

[Hsin-Yi Tsai (she/her) [:hsinyi]]

I cannot reproduce it after the blocker bug 1323400 is fixed.
Dear Daniel or Timea, would you please help verify it? Thanks!

Comment 7

[Daniel Bodea [:danibodea]]

Yes, of course. I have attempted to reproduce it on ARM laptop Lenovo Yoga C630 with Nightly v67.0a1 (2019-02-19) (aarch64 build) but it is not reproducing anymore.

I have also verified this issue on Microsoft Surface Pro 2 with Nightly v67.0a1 (2019-02-19) (win64 build, non-aarch64) and it is still not reproducing.

For personal investigation purposes, I have also verified whether there are changes in the behavior of the "normal" win32 build with a ARM laptop. It appears that the issue was also fixed there, but it can be observed that aarch64 build performs more "flowy" than the "normal" (non-aarch64) win32 build while navigating the Google Maps website, especially when using the zoom. The other build shows relatively small UI hiccups.

I will set this as WORKSFORME since it was fixed unintentionally. Please change it if incorrect.

Comment 8

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Thanks for the verification, Daniel. :)

One minor correction, this issue was not "being fixed unintentionally." We thought bug 1323400 could help here and it did as expected. :)