ahocevar
2991fa1178
Adding important comment
2012-09-26 22:39:21 +02:00
ahocevar
d6f6b828f1
preventDefault on mousedown
...
This is needed to avoid native image dragging.
2012-09-26 18:48:57 +02:00
ahocevar
47c343ce4f
We can rely on the click event
...
No need to use the mousedown/touchstart event here, because the click event gives us both clientX/clientY and button on touch devices.
2012-09-26 18:27:12 +02:00
ahocevar
5a97655983
Optimizing touch device handling
...
The native event of the touchstart/mousedown event needs to be cloned; change includes some compiler optimizations.
2012-09-25 18:30:23 +02:00
ahocevar
ce977e5364
Map browser event handling for touch devices
...
By handling click, dblckick and drag sequences in MapBrowserEvent, we can overcome closure issues with touch events. In particular, these issues were double drag events (from mousemove and touchmove) and a missing dblclick event on touch devices.
2012-09-25 17:28:01 +02:00
Tom Payne
f8c31ba45c
s/ol3/ol/
2012-09-24 14:21:41 +02:00
