# Disabling unload-on-scroll? **URL:** \ **Category:** UX\ **Created:** [December 22, 2020, 3:14am UTC](https://meta.discourse.org/t/disabling-unload-on-scroll/173975 "2020-12-22T03:14:26Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![ToyKeeper](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/toykeeper/32/297360_2.png) [@ToyKeeper](https://meta.discourse.org/u/ToyKeeper)\ **Post date:** [October 13, 2026, 4:54pm UTC](https://meta.discourse.org/t/disabling-unload-on-scroll/173975/4 "2026-10-13T16:54:11Z")
The “print” route is a good start, but still not really what I was looking for. In older versions, I could scroll to load an entire topic (or just the section which is relevant to a particular sequence), and keep it loaded, then use SingleFile to export an archive of the entire topic, displayed exactly as-is, as a regular forum page. Similar to a screenshot, but smaller, scrollable, zoomable, clickable links, save-able images, and text represented as text instead of pixels. Could also prepare the page first, doing things like expanding the “3 replies” widget, or un-hiding spoilers, or even attach private notes in the reply widget, to be viewed as part of the archive but never actually posted to the forum. Could also use uBlock Origin’s “zapper” to remove posts which aren’t relevant to the part of the topic I wanted to save… trimming the discussion down to just the exact comments I need. Then during a Discouse update, this ability was lost. The most I can get is a few posts at a time. Maybe more if I zoom out as far as the browser allows, to fit more posts onscreen. Would be awesome if there was a way to force it to stop unloading posts. Like, a hotkey or a button or a Konami code, or … whatever. Just press something to temporarily disable the javascript function responsible for unloading off-screen posts, for only this browser tab. For example, let’s say there is a 12,000 comment long topic about a group buy, spanning years, and then in the middle of it, people chat about cats for 100 posts before going back to the original topic. I could scroll to the beginning of the cat thread, press a “stop unloading posts” hotkey in Discourse, scroll down, use uBlock’s zapper to remove any posts which aren’t about cats, scroll to the end of the cat thread, then press the SingleFile hotkey to save the DOM as a .html file. I was able to do this as recently as last year; not sure when it stopped. Maybe it was only a bug which allowed it to work, since it looks like the unloading behavior already existed a decade ago. But I _liked_ that bug, and would like to be able to bring it back sometimes. I know it would make the tab use a lot more resources. That’s fine. There are use cases where “more content loaded in the DOM” is more important than minimizing RAM use. --- _[View the full topic](https://meta.discourse.org/t/disabling-unload-on-scroll/173975)._