Before you start please confirm the following.

• Yes, I've searched similar issues on GitHub.
• Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description

When viewing logs and not scrolled to the bottom of the log viewer, the scroll position keeps getting reset to the bottom.

Yes, I've searched similar issues on GitHub.

I have searched for similar issues and there are some reported but they are all reported as closed. I cannot find any open issues aside from #4338 which is a related but separate issue.

Expected Behavior

When viewing logs and not scrolled to the bottom of the log viewer, the scroll position should not be affected by the logs refreshing.

Actual Behavior

When viewing logs and not scrolled to the bottom of the log viewer, the scroll position resets to the bottom constantly, making it impossible to review old logs unless you uncheck "Auto-refresh logs". This is an unintuitive UX which was previously reported and fixed as part of #6797 and #7993.

Steps to Reproduce

1. Go to the log viewer for any container with multiple screens worth of logs.
2. Ensure that Auto-refresh logs is enabled (we do want to see new logs come in when we're scrolled to the bottom).
3. Scroll up and try to select some text from a few screens ago.
4. Watch as the log viewer jumps to the bottom automatically.

Portainer logs or screenshots

Portainer version

2.25.1

Portainer Edition

Community Edition (CE)

Platform and Version

Docker version 27.1.2, build d01f264

OS and Architecture

Linux entei 6.2.16-20-bpo11-pve #1 SMP PREEMPT_DYNAMIC PVE 6.2.16-20~bpo11+1 (2023-12-01T14:42Z) x86_64 GNU/Linux

Browser

Google Chrome Version 131.0.6778.204 (Official Build) (64-bit)

What command did you use to deploy Portainer?

No response

Additional Information

This bug appears to have been previously reported as an enhancement and marked as completed in both #6797 and #7993 (reported fixed in 2.17), but in the latest version (2.21.5) the issue is still here implying that the behavior has regressed and there's now a bug.