Replies (minor) snagging list.

[lampholder]

I built and tested the latest m.relates_to branches and hosted it on https://lant.uk/riot/new_replies

Things I tested:

• Replying to your own message ✅
• Replying to your own reply ✅
• Replying to a message from someone else ✅
• Replying to a reply from someone else ✅
• Replying to an emote ✅
• Replying to a picture ✅
• Replying to a file ✅
• Not being able to reply with an emote ✅
• Not being able to reply with a file ⚠️
• Replying on a narrow screen ⚠️
• Replying with a single emoji ✅
• Replying in an E2E room when there are unknown devices in the room ⚠️
• Representation on today's /app ✅ (In reply to link links to the original message)
• Representation over IRC bridge ✅ (reply is rendered sensibly)
  

In conclusion, for the most part it's great and nothing was show-stoppingly broken, but the ⚠️s represent tests where the outcome could have been a little bit better (mostly from a UX perspective).

Issues Identified

• P1 Reply UX slow to disappear - The replies UX was sometimes slow to disappear (taking ~a second to disappear after the reply has been sent)
• P2 Replying in an E2E room when there are unknown devices in the room - The current experience is:
  • initiate reply
  • type message
  • click send
  • receive 'unknown devices' prompt (which shows the reply as a red pending message, rather than a reply)
  • click 'send message'
  • message rendered to the timeline as a message
  • a few seconds later, the message appears (correctly) as a reply
• P2 Replying on a narrow screen - we get a return of the one-character-wide super tallness:
  
• P3 Not being able to reply with a file - If you open the reply function then upload a file, the file uploads behind the reply UX (and not as a reply). It is a known limitation of the current impl that we can't reply with a file, but the UX doesn't make that obvious (in the way that it does, say, for our not being able to reply with an emote).
• P3 Replying with a single emoji - it renders in the small style rather than the usual large style of a single... emojus

[Cadair]

I have just been giving this a little test a couple of quick thoughts:

1. there seems to be no way to click the rendered reply to jump back in the timeline to the location of the original message (to get extra context etc). Where as there is only this on /app currently, it would be nice if the (body of the) reply was clickable to jump back in the timeline imo.

2. When the in reply to of a reply to a reply is collapsed, the user pill is not clickable, either to take you to that user or to expand the reply. (I was expecting the latter)

Finally, I can't quite put my finger on what it is, but I feel that chains of two+ replies get's a little unclear. It's not visually obvious to me that I am effectively viewing a thread.

[t3chguy]

1. there is, its clicking the timestamp of the event being replied to, but agreed that is a little obscure
2. I shall investigate - thanks

[Cadair]

forgot to say in the original comment, but this looks awesome and I can't wait to have it!

[t3chguy]

message rendered to the timeline as a message

is VERY weird

[t3chguy]

oh I see why its happening, the local-echo does not include the m.relates_to because it gets stripped off to be put on the envelope event, so the local-echo needs to copy it accross

[t3chguy]

• there should be a way to collapse the thread when you're done with it

[lampholder]

I've stuck bug p1 major on this because all these minor snags being addressed added up to a major improvement on the replies UX

[t3chguy]

2. of @Cadair 's thoughts has broken out into #6670

[turt2live]

Not sure if the design is up for consideration as well, however I'm kinda a fan of this:

It feels like it takes up a lot less space, despite only saving a line or two.

[ara4n]

ironically i think that matches @jounih’s proposed design in the rework

…

-- Matthew Hodgson Matrix.org

On 10 Jun 2018, at 02:40, Travis Ralston ***@***.***> wrote: Not sure if the design is up for consideration as well, however I'm kinda a fan of this: It feels like it takes up a lot less space, despite only saving a line or two. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[aaronraimist]

When replying to a /me, the sent time is displayed on top of the avatar