You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Browser: Chrome Version 130.0.6723.70, other Chromium based (Edge): Version 130.0.2849.52 (Official build) (64-bit)
Any other tested browsers/devices(OK/FAIL):
FAIL: Chromium based i.e. Edge, Chrome
OK: Firefox (with one limitation: the touch simulation must be turned off(?) which seems counter-intuitive)
❗Disclaimer: based on the explanation here it would lead me to believe that it is also not correctly working in firefox(?) as it being enabled should then properly "translate mouse events into touch events." Which, if it is, does not work in ff then either. Though, when disabled, the fired events on the UI5 controls/item itself seem reasonable ...
URL (minimal example if possible):
DnD Samples, while found within sap.m.Tree, it does not matter I think:
User/password (if required and possible - do not post any confidential information here):
N/A
Steps to reproduce the problem:
Open up the application/demo
Try to simulate a touch-based device (hard refresh if you must)
Try drag 'n drop on your desktop
What is the expected result?
Working simulation for DnD to test, prototype and well all sort of thing you'd want DnD for ...
What happens instead?
Seems like the only "interesting" events that are triggered are scroll events (i.e. the touch/drag is interpreted as scroll?), at least in the chromium based browsers.
Any other information? (attach screenshot if possible) ⚠️This might, as described (+ mentioned in the title), not be a direct issue with UI5 itself but I've stumbled across similar touch issues in the past where you helped out opening an issue to chrome directly maybe this is another one of these lucky cases. If so I apologize for raising this here but still hope for someone can give a helping hand and once again raise this to the place where appropriate. ⚠️
Within chrome itself various options were tested:
going into "Sensors" and forcing touch like so
checking experimental flags like
also checked other places, settings (like in older versions of chrome the "Rendering" tab and so forth ..)
trying out different device types, even desktop + touch didn't seem to work
... all to no avail.
Here are also some quick screencasts thanks to @dfenerski for chrome & ff:
OpenUI5 version: latest (1.129)
Browser/version (+device/version):
Any other tested browsers/devices(OK/FAIL):
❗Disclaimer: based on the explanation here it would lead me to believe that it is also not correctly working in firefox(?) as it being enabled should then properly "translate mouse events into touch events." Which, if it is, does not work in ff then either. Though, when disabled, the fired events on the UI5 controls/item itself seem reasonable ...
URL (minimal example if possible):
DnD Samples, while found within
sap.m.Tree
, it does not matter I think:User/password (if required and possible - do not post any confidential information here):
N/A
Steps to reproduce the problem:
What is the expected result?
Working simulation for DnD to test, prototype and well all sort of thing you'd want DnD for ...
What happens instead?
Seems like the only "interesting" events that are triggered are scroll events (i.e. the touch/drag is interpreted as scroll?), at least in the chromium based browsers.
Any other information? (attach screenshot if possible)
⚠️ This might, as described (+ mentioned in the title), not be a direct issue with UI5 itself but I've stumbled across similar touch issues in the past where you helped out opening an issue to chrome directly maybe this is another one of these lucky cases. If so I apologize for raising this here but still hope for someone can give a helping hand and once again raise this to the place where appropriate. ⚠️
Within chrome itself various options were tested:
... all to no avail.
Here are also some quick screencasts thanks to @dfenerski for chrome & ff:
Screencast from 2024-10-23 19-51-55.webm
Screencast from 2024-10-23 20-02-47.webm
For a quick test in the
sap.m.Tree
sample, feel free to copy/paste (and remove uninteresting events):Maybe I found something, maybe I'm testing it wrong or expecting the wrong thing to happen. Happy for any input here! :)
The text was updated successfully, but these errors were encountered: