EPUB reader: click/tap-to-turn is disabled on my touch-capable laptop

[corygyarmathy]

What are you trying to do?

Click-to-turn pages in the EPUB reader when reading on my laptop in a web browser.

What's happening instead?

Cannot click-to-turn, have to use keyboard inputs to turn the page. Every click - regardless of where in the page it lands - toggles the toolbar instead.

Your setup

Version: 3.3.1
Installed from image: ghcr.io/grimmory-tools/grimmory:latest
Running on podman on my server
OS: Linux (Nix)
Device: Dell XPS 15 connected to Thunderbolt 3 dock (has touchscreen and trackpad - but I'm using it with the screen closed and docked)

Anything else that might help?

The EPUB reader docs details click zones without any caveats, with no mention of a device restriction or a setting to enable them:

Click Zones

• Left 30% of the page goes to the previous page
• Right 70% goes to the next page
• Tap the center to toggle the toolbar visibility

So either the docs are describing an intended behavior that isn't reaching me, or there are caveats that the documentation doesn't list. Please let me know if this is working correctly, and I'm just missing something.

Related:

• Configurable Tap/swipe page turning preferences #880 - reports that "...tap to turn a page does not appear to be available" and asks for configurable targets. Perhaps related? But I'm not asking for configuration options.
• [Enhancement] EPUB reader: tap to trigger next/prev page. #1876 - filed as an enhancement for mobile/PWA. I'm talking about for my laptop.
• feat(reader): add epub reader tap navigation for mobile #1909 - seems like it might address this. Its description is indicative: "...the zone-tap handler was gated to desktop only. On touch devices / the PWA every tap fell through to the center 'toggle toolbars' branch." Wondering if this means that because my laptop has a touch screen, it's being treated like a mobile / touch device? It seems the PR is being treated like an optional-mobile enhancement, but I'm wondering if it may be more important if it fixes this behaviour.

Disclaimer: used AI (Claude Code) to troubleshoot and research the issue, mostly to narrow down whether it was my computer, my server, my configuration, or Grimmory - but I have written this discussion manually. It highlighted what it thought to be specific issue in the code, but I will not include that here b/c I haven' taken the time to understand it (but it seemed to be what is being addressed in the linked PR).

Before submitting

• I've searched existing discussions and I can't find anything that looks like my problem
• I've reviewed this report and have completed it as fully as I can