[MGNLUI-3693] Research why mouse isn't working on a touch device Created: 01/Dec/15  Updated: 08/Feb/17  Resolved: 08/Feb/17

Status: Closed
Project: Magnolia UI
Component/s: page editor
Affects Version/s: 5.4.3
Fix Version/s: None

Type: Task Priority: Critical
Reporter: Andreas Weder Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: blocked, page-editor, support, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
duplicate
duplicates MGNLUI-3678 No component edit bars (Chrome, hybri... Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

A customer has reported that the mouse doesn't seem to work in the page editor, if the device used supports both touch and mouse input. The edit bar simply don't seem to respond to any clicks.

Please perform a quick research as to why this happens. If possible, please also suggest a way to remedy this problem.



 Comments   
Comment by Christopher Zimmermann [ 20/Jan/16 ]

I ran into this recently on another project.
The culprit on my project was this outdated logic:
Detect if device supports touch.
If so - handle touch events (so that UI responds faster.)
If not - handle mouse events.

New logic should simply be to handle both types of events regardless of capability - but touch handler should call preventDefault so that the event isnt handled again when the mouse event fires.
Described well here: http://www.html5rocks.com/en/mobile/touchandmouse/

Generated at Mon Feb 12 09:09:11 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.