Closed Bug 1848556 Opened 1 year ago Closed 10 months ago

In Thunderbird v115 , Last Read Message Requires Manual Scrolling to View

Categories

(Thunderbird :: Folder and Message Lists, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: michael, Unassigned)

References

Details

(Whiteboard: [closeme 2023-11-22])

Steps to reproduce:

Updated to Thunderbird v115 on a Windows machine and on a MacOS Machine.
Opened Thunderbird and navigated to a folder with multiple messages.
Read all new messages ensuring the last read message was visible at the bottom.
Closed and restarted Thunderbird.
Reopened the same folder within Thunderbird.
-> Occasionally, the last read message is displaced, appearing below the visible portion of the folder window, mimicking a user scroll action.

Actual results:

Upon reopening the folder after the Thunderbird restart, the last read message was displaced and appeared below the visible portion of the folder window. I had to manually scroll down to view the last read message. (scroll down very old messages)

Expected results:

After restarting Thunderbird and reopening the folder, the last read message should have been automatically visible at the bottom of the folder window without requiring manual scrolling.

I see the same, when in View -> Density -> Compact mode the mail list positioning seems wrong, the end always lands out of the visible area - in View -> Density -> default mode all works correctly as expected.

(Linux, Debian Unstable, Thunderbird 115.1.0)

Addon: Not sure if this could be affected by my advanced setting of layout.css.devPixelsPerPx = 1.10

See Also: → 1837771

How is the most recent beta / release ?

Addon: Not sure if this could be affected by my advanced setting of layout.css.devPixelsPerPx = 1.10

Could be.

Severity: -- → S4
Flags: needinfo?(michael)
Flags: needinfo?(mail-mozilla)

Similar experience here. In a long list of messages I have to scroll one third of the list to get to the latest message. Had this issue also with the first official build of Supernova and uninstalled it right away - very nasty bug.

My installation is not fresh, I have multiple accounts configured. Default density.

Thunderbird 115.3.1, Win 10

I have discovered that this unwanted behaviour was probably triggered by leftovers from my userChrome.css file from previous installation.

PS I wish I knew a working solution how to restore messages list density know from thunderbird versions prior to 115: messages list density like in default view, folders density like in compact view.

See Also: → 1827042

(In reply to Haegar from comment #1)

I see the same, when in View -> Density -> Compact mode the mail list positioning seems wrong, the end always lands out of the visible area - in View -> Density -> default mode all works correctly as expected.

(Linux, Debian Unstable, Thunderbird 115.1.0)

Addon: Not sure if this could be affected by my advanced setting of layout.css.devPixelsPerPx = 1.10

Ideally this should be allowed to default. Otherwise, the new code in version 115 may not behave as expected.

Flags: needinfo?(michael)
Flags: needinfo?(mail-mozilla)

Michael,

Thanks for the bug report.

Is your issue better or worse after recent version 115.4.3?
And is mailnews.scroll_to_new_message set to false or true? It will be the default value of true unless you changed it.

Flags: needinfo?(michael)
Whiteboard: [closeme 2023-11-22]

We do rely on your feedback to keep the bug report moving forward. This is incomplete without further feedback.

Status: UNCONFIRMED → RESOLVED
Closed: 10 months ago
Flags: needinfo?(michael)
Resolution: --- → INCOMPLETE

(In reply to Wayne Mery (:wsmwk) from comment #7)

We do rely on your feedback to keep the bug report moving forward. This is incomplete without further feedback.

Hi Wayne Mary,
I've checked the issue I've reported in the latest version 115.4.3 and it appears to have been resolved.
Thank you so much :)

Thanks for the update.

Resolution: INCOMPLETE → WORKSFORME
You need to log in before you can comment on or make changes to this bug.