aboutsummaryrefslogtreecommitdiffstats
path: root/android/app/src/twa/java/io/coinos
diff options
context:
space:
mode:
authorAdam Soltys <[email protected]>2026-10-16 22:13:16 -0700
committerAdam Soltys <[email protected]>2026-10-16 22:13:16 -0700
commit7d09e7f2b01f72db518f7cf906d887c22a49387e (patch)
tree2ea6d565bf6518ca6c471b43a339a710d3f90024 /android/app/src/twa/java/io/coinos
parent550bd5cb8be1a879083d987edca7b4e676ac3557 (diff)
downloadcoinosv3-7d09e7f2b01f72db518f7cf906d887c22a49387e.tar.gz
coinosv3-7d09e7f2b01f72db518f7cf906d887c22a49387e.zip
The wheel coasts wherever the pointer is while a feed or a thread is up.
The coast only took a notch whose target sat inside the feed or the thread, so a pointer resting on the rail, the header or the wallet column beside the feed on a wide screen got the browser's plain scroll (Adam, 2026-10-16: "when my cursor is hovered over the right side bar or any part of the page that's not the feed, wheeling scrolls without coasting. can we make it coast no matter where my pointer is?"). Now the question is whether a feed or a thread is the page on screen; the pointer's spot only matters when it is over something that takes the wheel itself — a text box, the chips strip, the lightbox, the pager, a box that scrolls on its own — and on a page with no feed on it (the wallet) the wheel stays the browser's. feed-wheel-reverse-test: the fixture's page carries a feed unless told otherwise; a notch with the pointer over the wallet column, or over nothing in particular, coasts; one on a page without a feed does not. Co-Authored-By: Claude Fable 5.1 <[email protected]> Claude-Session: https://claude.ai/code/session_01J1Kon8bxJoHRpJdSzshCkp
Diffstat (limited to 'android/app/src/twa/java/io/coinos')
0 files changed, 0 insertions, 0 deletions