Return to most recent position in conversation after viewing multimedia element

[SilverPuppy]

Checklist

• I made sure that there are no existing issues - open or closed - to which I could contribute my information.
• I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
• I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.
• I optionally donated to support the Fossify mission.

Feature description

Presently, when one scrolls back in the conversation, finds a multimedia element, such as a picture or bit of audio, opens it, upon returning to the list, it returns to the present. This means that if multiple multimedia elements are next to each other, a lot of scrolling is required to view them, as the position is lost upon viewing each element. Audio is rather visually comical, as my config opens the audio in the background with VLC, but the conversation jumps back to the present before my very eyes.

Why do you want this feature?

Making the conversation stay where it was left during this sequence would make it much more usable. As it is, reviewing the past multimedia elements is very impractical.

Additional information

No response

[Aga-C]

This problem is not necessarily with multimedia only. It also loses position when going back to app from Recent Apps, even if conversation has only SMS messages. 
It seems to be related to messages lazy loading, because it only happens if I scrolled so much to the top, that the loader had appeared to load more messages.

[SilverPuppy]

This also isn't limited to viewing. If I long press and save an image, it also jumps the conversation back to the present. This is extremely frustrating if I'm trying to save (or view) multiple things from the past.

[primesun]

The original bug report doesn't list app version etc. so I'll just add mine as I can confirm that this affects me too on the current latest version:

App version 1.1.5
Android 15
Pixel 6a