[Chrome] Touch dragging donesn't work on fullscreen
Reported by
grp-adob...@adobe.com,
May 24 2017
|
||||
Issue descriptionChrome Version: (copy from chrome://version) OS: Win8 and above FAIL: Win10 / Chrome: 58.0.3029.110 and Canary 60.0.3103.0 / FP: 19.0.0.245 to 25.0.0.110 FAIL: Win 10 64-bit with Touch support / Chrome: 58.0.3029.110 / FP: 26.0.0.115 FAIL: Surface Studio, OS: 16199 / Chrome: 58.0.3029.110 / FP:25.0.0.171 FAIL: Win 10 Ent 64-bit / Chrome: 59.0.3071.61 / FP: 26.0.0.115 FAIL: Surface Book ver 15063.138 / FP: 25.0.0.171 / Chrome: 58.0.3029.110 PASS: Working on Firefox What steps will reproduce the problem? (1) Visit http://dev.biomedia.nl/drag/ (2) Drag circle using touch (3) Switch to fullscreen mode and drag circle using touch What is the expected result? User can drag circle on both fullscreen and non-fullscreen mode What happens instead? (3) Circle can't be dragged on fullscreen mode Please use labels and text to provide additional information. Here is the CHANGELOG URL: You are probably looking for a change made after 445294 (known good), but no later than 445295 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/f771194423dfad6736b846e2bf3417b2e021a798..1d97062b110831423488e9bc5bd67a1bde1fded5 For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report.
,
May 24 2017
,
May 30 2017
Is there a reproduction of this bug without using Flash?
,
Jun 1 2017
I tried printing the mouse down/move/up/wheel events in a javascript/html version. They seem to be working the same in fullscreen and non-fullscreen, but in javascript the mousemove event is not fired continuously when moving a finger on a touchscreen, only once before down/up events. In flash when an object is in drag mode it will continuously fire mousemove events so this is a little different. (Btw this bug report is based on my own bug report in adobe's bug tracker (https://tracker.adobe.com/#/view/FP-4198432)
,
Jun 1 2017
+ dtapuska@ and mustaq@ Any chance we're doing some sort of coalescing/throttling of the touch events here? Since there's no OOPIF involved, the net effect of my CL would only be to move the ownership of the input event handler from RenderView to RenderWidget ... I'm not sure what implications that might have for the fullscreen case.
,
Jun 1 2017
My best guess it is related to the part of the change where you move around whether the page has a touch event listener or not (WebViewImpl and the chrome client stuff).
,
Sep 19
|
||||
►
Sign in to add a comment |
||||
Comment 1 by lafo...@chromium.org
, May 24 2017Owner: wjmaclean@chromium.org
Status: Assigned (was: Untriaged)