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
Hi,
When dragging a picture from Nautilus, Cheese (webcam photobooth) etc. to Revolt, the cursor turns from a mouse to a green + sign, but in completely unpredictable ways and in very small parts of the Revolt interface. This means unless you happen to land on a "green +" area by luck, you are left with trying to move your mouse bit by bit until you land on an area where Revolt will let you upload the pic.
More often than not, that's a waste of time, and you're better off just using the normal "upload file" button in the Riot interface.
I have noticed this myself, and it happens with WebKitGTK+ based browsers as well (like Epiphany / GNOME Web). It needs investigating, my suspicion is that either WebKitGTK+ is not handling something 100% correctly when it comes to drag-and-drop targets, and if one looks at what seems to constitute a valid target, for example the horizontal lines which separate days are “easier” to hit as drop target, which makes me think that there is something fishy going on with elements that have transparent backgrounds (or no background set).
Interestingly enough, drag-and-drop of images into the GitHub comment composition box works flawlessly. It may be worth it to check out how its handling of the drop area is different from Riot's.
Hi,
When dragging a picture from Nautilus, Cheese (webcam photobooth) etc. to Revolt, the cursor turns from a mouse to a green + sign, but in completely unpredictable ways and in very small parts of the Revolt interface. This means unless you happen to land on a "green +" area by luck, you are left with trying to move your mouse bit by bit until you land on an area where Revolt will let you upload the pic.
More often than not, that's a waste of time, and you're better off just using the normal "upload file" button in the Riot interface.
May or may not be related to #26.
The text was updated successfully, but these errors were encountered: