Room list tag state change on drag and drop is glitchy.

[lampholder]

Dragging roomtiles from one section to another results in their having the wrong tag.

[lampholder]

My starting setup was:

INVITES
(#) Test Room
FAVOURITES
(#) Matrix HQ
PEOPLE
(#) Riot-bot

I dragged Matrix HQ from FAVOURITES to PEOPLE, then I waited for a bit, then Matrix HQ ended up in ROOMS.

Further dragging and dropping caused similar unpredictable behaviour.

[lukebarnard1]

• So dragging Rooms -> People was broken: Fix broken import preventing people tag matrix-org/matrix-react-sdk#1811
• Dragging from FAVOURITES to PEOPLE has always resulted in the thing being put into ROOMS

[lampholder]

I've found another problem in a similar space (which maybe should be a separate bug but I'm putting it here for now):

If you're roomlist looks like this:

And you drag Riot onto the "You're not in any rooms yet!' landing rectangle, it gets stuck on the ROOMS header like this:

It fails with this error:

[lampholder]

Also I noticed that you can't drag into historical, but it turns out you can't do that on /app, either.

[lukebarnard1]

FTR: Same bug

[lampholder]

The room list is a mess of UX paradigms - four headings that look the same (five if you count invites) and they all work a little bit differently.

INVITES - No dragging; disappear after accepting/rejecting
FAVOURITES - Drag within the list to set order manually. Drag outside of list to change DM/not DM, Favourite/Not Favourite and Low Priority/Not Low Priority state.
PEOPLE - rooms end up here based upon unclear (to the user) heuristics. No dragging within list. Drag outside of list to change DM/not DM, Favourite/Not Favourite and Low Priority/Not Low Priority state. Ordered by most recent activity.
ROOMS & LOW PRIORITY - No dragging within list. Drag outside of list to change DM/not DM, Favourite/Not Favourite and Low Priority/Not Low Priority state. Ordered by activity.
HISTORICAL - No dragging of any sort, in or out.

Add to that that some transitions don't work - this is clearly an area that needs some attention 😄

[lampholder]

The wider scope of this issue wasn't a release blocker in the end - they were issues that had been in place from before 0.14 (and I didn't want to block 0.14 on their resolution).

[turt2live]

Closing in favour of #8614