Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When jumping to an event, have the "go back" button go back to the message you jumped from #1572

Open
ShadowJonathan opened this issue Aug 3, 2021 · 1 comment
Labels
O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Low/no impact on users T-Enhancement X-Needs-Design

Comments

@ShadowJonathan
Copy link

Is your suggestion related to a problem? Please describe.

If I click on a reply, a permalink, or anything else that jumps me to a message, and i want to back, the "go back" button in the bottom right takes me back to the bottom of the timeline.

Describe the solution you'd like.

Have, when jumped to a message from a previous message, the "go back" button jump to the message that was being jumped from.

Telegram exhibits this behaviour, and it makes "arbitrary jumping" through the timeline much easier to reason about.

Bonus; Telegram also does this (implicitly) on a stack-based approach, i.e. when you scroll up, jump to message X from A, then scroll up more, and jump to message Y from B, when you press "back", you end up at B, and when you press back then again, you end up at A;

()
> jump to X from A
(A) // view currently at X
> scroll up
> jump to Y from B
(A, B) // view currently at Y
> press back
(A) // view currently at B
> press back
() // view currently at A
> press back
> (no more messages in the stack, go to bottom of timeline)
() // view currently at bottom of timeline

(This "stack" should also empty if the user (via some way) ends up at the bottom of the timeline again, this is to prevent bugs and weird UX behaviour)

@ShadowJonathan
Copy link
Author

ShadowJonathan commented Aug 3, 2021

(I think this addresses some discomforts that have existed for long, but were never addressed, and became more apparent when the new reply design came up, and so I view this is an alternative to element-hq/element-web#18179 and element-hq/element-web#18200)

@novocaine novocaine added O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Low/no impact on users labels Aug 4, 2021
@t3chguy t3chguy transferred this issue from element-hq/element-web May 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
O-Frequent Affects or can be seen by most users regularly or impacts most users' first experience S-Tolerable Low/no impact on users T-Enhancement X-Needs-Design
Projects
None yet
Development

No branches or pull requests

3 participants