mirror of
https://github.com/advplyr/audiobookshelf.git
synced 2026-05-30 23:40:40 +02:00
[Bug]: UI mouse navigation with Back / Forward buttons, do not work when pointer is over an audiobook image (works okay over authors or other pagespace) #2000
Reference in New Issue
Block a user
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 @DavidPesticcio on GitHub (May 21, 2024).
What happened?
While using the mouse to navigate back a page or forward a page in browsing history, the buttons do not function if the mouse is focused with the "hand-finger" pointer, e.g. while over an audiobook image or text - although it appears to function just fine while over an author image, or other non-image parts of the pagespace where the pointer has the "default" pointer.
The behaviour is observed while on the Home, Library, Series, or Collections pages.
What did you expect to happen?
The mouse back and forward buttons should cause the page to change back or forward according to the browsing history.
Steps to reproduce the issue
Audiobookshelf version
v2.9.0
How are you running audiobookshelf?
Docker
What OS is your Audiobookshelf server hosted from?
Linux
If the issue is being seen in the UI, what browsers are you seeing the problem on?
Chrome
Logs
Additional Notes
N/A
@DavidPesticcio commented on GitHub (Jan 24, 2025):
Issue still present in v2.18.0
@DavidPesticcio commented on GitHub (Feb 15, 2025):
Issue still present in v2.19.2
@DavidPesticcio commented on GitHub (Feb 21, 2025):
Issue still present in v2.19.3
@DavidPesticcio commented on GitHub (Aug 4, 2025):
Issue still present in v2.26.0
@Vito0912 commented on GitHub (Aug 4, 2025):
Hey,
the newest server version is v2.27.0. Apart from that unless mentioned in the release notes that the issue is fixed there is no need to add new comments. Issues get sorted by thumbs up and not comments FYI
@DavidPesticcio commented on GitHub (Sep 10, 2025):
I just happened to test this on Firefox 142.0 (64-bit) and the issue does not exist.
It still exists in Chromium Version 139.0.7258.154 (Official Build) (64-bit) though.