mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 16:56:00 +03:00
[GH-ISSUE #272] Ux improvement: view previous message button could update when there's a new email available #178
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#178
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @epicwhale on GitHub (Mar 30, 2024).
Original GitHub issue: https://github.com/axllent/mailpit/issues/272
Just sharing a productivity pain point, incase others face it too:
The "View Previous Message" button (triangular left arrow) does not update in tandem with the "Return" button indicating there is a 'newer email' available.
Left action disabled

Despite

So to quickly access the latest email, I need to go back to the main inbox view, and then tap.
Expected: Triangular left arrow button at top right is available whenever a new mail is detected, so can jump to it directly.
@epicwhale commented on GitHub (Mar 30, 2024):
Oops, I just spotted the popup that appears when new mails arrive at the bottom right (missed it on my large monitor earlier). That does the job!
@axllent commented on GitHub (Mar 31, 2024):
@epicwhale Thanks for the feedback. Yes, I am aware of this "issue", but it's more of an "issue by design" than an oversight/bug. When a message is clicked in the message listing, the
<prev>-<next>button logic is taken from the current view, and not dynamically changed when new messages are received. The reason is that the message listing can change very quickly (between 100-200 messages per second) which would completely change the logic of what is the next message on that page - so what you are viewing may not even be listed on on the current page any more (moved to another page based on the number of messages per page).It is not ideal, I know, but the confusion it would potentially cause if it dynamically changes on every new received message is not worth it. As you've seen, there are notifications when new messages are received, so this is one of the work-arounds to at least allow a user to load the latest message while viewing another.