Disruption to CTRL+F search, pls provide alternate method

joesmith3129857
Wed, 07 Jan 2026 14:54:44 +0000
Support

Hi,

I was on the following discourse forum

OpenWrt Forum – 7 Jan 26

Re: LUCI - add support for managing tags in DHCP and DNS configuration web page

Feature Requests

Hello, It possibly is when the dhcp_redesign_phase2 branch was deleted on possibly commit 0bf2ea9. I say possibly because this is what I have in some text file, but I can’t verify it anymore and I don’t remember where I got it. Here is the...

And I needed to find the word “mac”

Using CTRL+F, it could only find this string when it was on screen. Scrolling itself made matches disappear.

It also disrupts the scroll position match indicator in the scroll bar

I understand the claim that this is to “save memory”, but this system has 64 gigabyte of memory and this page is less than 100 kilobytes of text. So I understand that this is actually and anti-scraping feature like facebook utilises to prevent (but fail) scraping.

Searching for this strange bug, I found an absolute sea of complaints about this extremely disruptive anti-feature.

What are the alternatives ?

Can it be disabled client side ?

What about loading the page in print mode ?

Is there any way to force a full text only dump of the entire page so I can just view it in a text editor ?

What about greasemonkey script, anything that can break the feature that unloads from memory the text so it can be searched ?

Is my only option to penetrate the database server, exfiltrate all discourse content and then write code to display the comment thread without these disruption ?

I see complaints about this from 2014, so I imagine there is no desire to solve this issue and it’s a “feature not a bug” but a feature for the owners not the user ?

What is the “meta” on this very serious problem that makes me DREAD ever having the misfortune of having to navigate a “discourse” forum ?

Yes, I’m bitter, how can you tell ?

9 messaggi - 3 partecipanti