The timeline scroll view doesn't start at the bottom after opening a notification

[Anderas]

Steps to reproduce

1. Send a multiline message from device A (it should be at least 3+ lines long)
2. Observe a notification on device B
3. Open the notification and wait until the room is shown
4. Notice that the room is not scrolled all the way to the bottom

Outcome

What did you expect?

The timeline shows the most recent message

What happened instead?

The timeline is scrolled up, not displaying the most recent message

Your phone model

No response

Operating system version

No response

Application version

No response

Homeserver

No response

Will you send logs?

No

[Anderas]

@AverageMarcus would you be able to provide more details for this issue, e.g. type of device you are using, exact steps to reproduce, possibly a video. I am unable to reproduce the issue atm.

[AverageMarcus]

Sure, I'll add what I can now.

What did you expect?

When clicking on a notification the timeline should be scrolled to the first unread message

What happened instead?

The timeline is scrolled up, not displaying the most recent message

Your phone model

iPhone 12

Operating system version

iOS 15.3.1

Application version

1.8.1

[AverageMarcus]

Video (slightly edited to remove personal info)

RPReplay_Final1645439699.mp4

[bionemesis]

Not sure if @AverageMarcus can confirm, but we tested this internally and at first it appeared to be fixed but then after about a day it started happening again. When we click on a notification, instead of going directly to the message it goes to an arbitrary spot in history. We confirmed all our devices are on 1.8.3.

[AverageMarcus]

Yeah, still an issue for me with Element 1.8.3 also.

[Anderas]

Thanks for reporting this, I am reopening the issue

[Anderas]

Looking at this issue again I am not able to reproduce this atm. Could you please confirm whether this is still happening in the latest version and if it is provide further steps to reproduce above and beyond those described in the header?

[AverageMarcus]

I’ve just updated to 1.8.7 and I think this now might be fixed. Haven’t been able to reproduce it since so I think we’re good to close this now. 😄

[Anderas]

Ok great. If you do encounter this issue again, please provide as specific steps to reproduce as possible, assuming that it would not be obvious to reproduce.