Follow-up: chat scrolling refactoring

[DorraJaouad]

☑️ Resolves

• follow-up to chore(MessagesList): Refactor scrolling #11934

TO-DO

• 👷🏻‍♀️ Refactor
• ⚠️ Fix conversation jumping on opening
• 🔴 Empty content is not shown anymore because of loadedMessages flag does not change to true in empty conv
• 💚 Addition: add a floating button at the bottom in case you are scrolled up and new messages come in ( aka indicator for new messages while opening the chat in top)

🖌️ UI Checklist

🖼️ Screenshots / Screencasts

Conversation switching before

Recording.2024-04-19.before.mp4

Conversation switching after

Recording.2024-04-19.after.mp4

🏁 Checklist

• 🌏 Tested with Chrome, Firefox and Safari or should not be risky to browser differences
• 🖥️ Tested with Desktop client or should not be risky for it
• 🖌️ Design was reviewed, approved or inspired by the design team
• ⛑️ Tests are included or not possible
• 📗 User documentation in https://github.com/nextcloud/documentation/tree/master/user_manual/talk has been updated or is not required

[DorraJaouad]

ChatIdentifier is updated on two steps:

1. {token: 't3qj6xtm', isParticipant: false, isInLobby: false}
   Chat is not scrolled yet because , the condition in handleStartGettingMessagesPreconditions is faulty
2. {token: 't3qj6xtm', isParticipant: true, isInLobby: false}
   this is when the chat is finally scrolled

isParticipant is not updated instantly, need to find workarounds to make it available

UPD; or just ignore it :p. It is not needed in handling opening conversations. If the user is actually not a participant, it seems blocked by API. --> dropped this idea because it might lead to brute force protection triggered.

UPD2: used conversation store, as it is instantly available

[DorraJaouad]

Focused message from URL doesn't focus correctly sometimes 🥲
--> Fixed

[Antreesy]

Checked only the last commits (unrelated to scrolling logic):

[Antreesy]

As discussed during pair-review, seems to work much better. Seems that even the opening of every chat at the top is resolved! One more thing to try to reproduce and fix:

[Antreesy]

I'm quite impressed with the final result, to be honest =P

cc @nickvergessen @ShGKme @danxuliu : I'd suggest to look through it once more thoroughly (maybe after RC), and at best - compile the desktop client with this PR and use it for a while. If we consider it good enough, then could backport for 19.0.1

[DorraJaouad]

/backport to stable29