The irony that this particular instance of discourse must have disabled this feature is not lost. Have the powers that be around here recognized its inferiority?
When you do this, to improve scrolling & rendering performance, Discourse removes earlier posts from the DOM. So it is impossible to ‘load all’ of a large topic.
That’s why we have the custom ctrl+f implementation, and we only use it for long topics which are impossible to load in their entirety.
Seems to me like you’re just making excuses. Hijacking native functionality should be a hard no. 99.9% of sites on the internet respect this. Why is discourse special?
What keystroke would you recommend for people who expect control-F to find the post they are looking for in the topic when that post isn’t available in the browser. It would seem like what you would expect is for control-F to find the post you want in that topic, but that’s not what you want. What’s the “find the post in this topic even if my browser can’t find it” key? Isn’t having control-f not find a post in the current topic a violation of expectations?