Help shape PageMarks before launch: what breaks scroll restore?
Hey everyone — I’m building PageMarks, a Chrome extension that saves exact scroll positions (multiple per page) so you can jump back to the exact spot later, with optional notes/tags. Before launch I want to make sure the core “restore” works reliably, so I’d love your input: (1) which sites are the hardest for scroll restore (infinite scroll, SPAs like Notion/Docs, pages that reflow images/ads, etc.) and what symptoms you see (wrong position, drift, jumps, stuck loading)? (2) what would make this genuinely daily-use for you: keyboard shortcuts, folders/projects, per-site defaults, export/backup, sync, etc.? (3) what’s the cleanest onboarding/UX for “add marker → manage → jump back” without getting in the way? If you’ve got a problematic site, drop the URL + what you did (e.g., “scroll to section X, refresh, reopen”) and I’ll try to reproduce it.


Replies