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
Reported by rainforest1155 on 13 Nov 2013 23:05 UTC as Trac ticket #1489431
While you can drag a message around on the screen and moving it over a folder, it does indicate that the message can be dropped into the folder, the message isn't actually getting moved. It just remains where it was before you attempted to move it.
This happens on the default and Larry theme in Safari on my iPad1 (iOS 5.1.1 - latest version available for device) and iPhone4 (using iOS 6.1.2). I've also tried an alternative browser (Atomic Web), but the issue is still the same.
So right now a message needs to be opened with a double click and then one can use the move drop down menu to move it to another folder.
Not a solution for this issue, but we already implemented a menu in main mail interface with copy and move actions, so you don't need to use drag-n-drop.
Fixed in commit 001e39e. The application script now uses the dragend callback from the list widget instead of a self-registered document.onmouseup event which doesn't fire on touch devices.
Reported by rainforest1155 on 13 Nov 2013 23:05 UTC as Trac ticket #1489431
While you can drag a message around on the screen and moving it over a folder, it does indicate that the message can be dropped into the folder, the message isn't actually getting moved. It just remains where it was before you attempted to move it.
This happens on the default and Larry theme in Safari on my iPad1 (iOS 5.1.1 - latest version available for device) and iPhone4 (using iOS 6.1.2). I've also tried an alternative browser (Atomic Web), but the issue is still the same.
So right now a message needs to be opened with a double click and then one can use the move drop down menu to move it to another folder.
Keywords: Move,message,mobile
Migrated-From: http://trac.roundcube.net/ticket/1489431
The text was updated successfully, but these errors were encountered: