Closed Bug 1786302 Opened 2 years ago Closed 2 years ago

Vertical scrollbar moves to top when activating message tab

Categories

(Thunderbird :: Message Reader UI, defect)

Thunderbird 102
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: stepand76, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:103.0) Gecko/20100101 Firefox/103.0

Steps to reproduce:

  1. Open a long message in a new tab.
  2. Scroll to the end of the message.
  3. Activate previous tab.
  4. Activate the previously created tab again.

Actual results:

Vertical scrollbar position is reset to the top when the message tab is activated.

Expected results:

It should keep the scrollbar position.

This didn't happen in version 91?

Flags: needinfo?(stepand76)

Not sure, but I don't think so. Now I'm running 102 and not going to switch back. However I don't like that behavior. Imagine this in Firefox...

Flags: needinfo?(stepand76)

To clarify the STR: It isn't necessary to scroll to the bottom to see the issue. Visiting the tab shows the top no matter where the scroll bar was left in the previous viewing of the message.

Reporter, do you still see this issue when using the latest version?
What information can you add to clarify the steps to reproduce this issue?

Whiteboard: [closeme 2023-04-25]

I just reproduced this with 102.9.0 on Ubuntu.

Steps to reproduce:

  1. Open a long message in a new tab.
  2. Scroll down in the message.
  3. Return to the primary tab.
  4. Return to the message tab.

Expected:
4) The scroll position in the message tab is the same as was left in step 2.

Actual:
4) The message is scrolled to the top of the tab.

Can this be reproduced with beta?

I cannot reproduce the issue with 114.0b1.

But using messages in tabs with 114.0b1 is frustrating in a different way. See bug 1833134.

Resolved per whiteboard and Comment 8

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2023-04-25]
You need to log in before you can comment on or make changes to this bug.