This turned into a rant, sorry
What do you guys think ? Does this sort of thing bother you too, do you take it into account in your developments ?
ctrl+f will be quirky here because only the visible-ish part of the stream you are wading in is loaded at any given time.
Imagine a topic with 3,000 replies. Would all those be on the same “page”? (This will actually work OK on very small topics since the stream is so small it is actually all loaded on the page.)
We’ve talked about capturing ctrl+f and having it open the search button in the upper right.
There should be absolutely no issue with the back button, and that’s a far more critical piece than a keyboard shortcut most average folks don’t even know exists. Open as new tab will also work fine, with a caveat around a quirk of Firefox.
(Was going to start a new thread, but since this one’s right here…)
I have two issues here.
One, loading 3000 replies at once would indeed be a problem, but no thread in the (short) history of the BoingBoing BBS has as many as 500, and only 19 have more than 200. There’s got to be a happy medium between “load every single post in the entire thread” and “only load the posts that are visible on the current screen.” 100-200 posts are a time seems like it would work (although it might trip people up on longer threads, if they got used to searching normally and didn’t realize that it breaks on long threads).
Two, it’s not just that it only loads the current screen, it’s that it UNloads everything that’s not the current screen. I can understand wanting to reduce needless bandwidth, but right now, if I start at the beginning of the thread and page-down to the end, I can still only search the current screen or so. That means you’re making my browser throw out a bunch of data that it’s already received. If I page back up to the top of the thread, you’ve had to send me the entire thread twice for no good reason. Allowing posts, once loaded, to remain so would both save on bandwidth and let people Ctrl-F properly once they’d flipped through the entire thread once. That seems desirable.