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
Today I encountered an issue where Element X showed a loading placeholder for a reply to a message that wasn't available to my client.
Ignoring the fact that it didn't transition to some kind of failure UI, @BillCarsonFr pointed out that there's the fallback reply which is always available in an event:
Which leads me to realise that if we included the (properly extracted and formatted) fallback reply in the InReplyToDetails we could render this while loading the actual event (and if the load fails, there is still something to show).
The text was updated successfully, but these errors were encountered:
Today I encountered an issue where Element X showed a loading placeholder for a reply to a message that wasn't available to my client.
Ignoring the fact that it didn't transition to some kind of failure UI, @BillCarsonFr pointed out that there's the fallback reply which is always available in an event:
Which leads me to realise that if we included the (properly extracted and formatted) fallback reply in the
InReplyToDetails
we could render this while loading the actual event (and if the load fails, there is still something to show).The text was updated successfully, but these errors were encountered: