Did you get a chance to try TK’s themes yet in the bottom of the sidebar?
Yeah, using it now, its an improvement but not quite there.
And the colours need some work.
In regards to the slider instead of pages, frankly i prefer pages but i do agree that it has issues of its own, i have had to deal with some on other sites, for example i had mine set to 50 posts per page and the forum default was 20, every time someone linked a post it would glitch. So i eventually had to reset mine to match to make it work, though others who have a different number still glitch then they post a link.
My biggest issue with that is that if i use the Firefox slider it does not match up well, especially if i try to scroll to top. I don’t think its a bug per se, but i would be nice if a suggestion could be made that they design it so if i scroll to top in Firefox it scrolls to Post number 1 of the thread.
That said thats small potatoes.
Feel free to suggest color changes here:
I believe the reason they don’t do that is because it would be too much information to load into the browser’s page buffer. Like imagine a 2000 post thread with the post #1 being at the top of the Firefox scrollbar and post #2000 at the bottom. So it loads the thread into chunks, and the browser’s scrollbar moves between those chunks.
Yeah, this is very annoying. I am kind of used to it since i’ve seen it on other forums, but it always makes me wonder - are our modern devices with all the gigabytes of memory and multi-core CPU-s (yes, even phones) really incapable of loading and displaying few MB of text? Or how much would something like 1000 posts/page be? Probably even less…
Will check it out.
BTW any luck getting the multi quoting issue addressed, i don’t always remember to type some dummy letters after a first quote so i can go back and make other quotes.
That makes sense but then it actually supports having pages.
But since i can do it in the forum but not in Firefox its strange there is a difference/problem.
I know some forums have gotten around the page issue glitch i mentioned by linking to the post not page/post. But then again thats presumably on the Discourse programmers side and not yours.
Hmm first time I’ve heard of the issue. I just tried it and everything seemed normal.
I had made a thread about it and this post mentioned the workaround
Ah yes, but I thought that was just a matter of not minimizing the post editor since the it allows for viewing/scrolling the thread simultaneously while the editor is open. Or is there a specific reason for minimizing the editor?
So that i can write posts full screen instead of split screen.
I often tend to be verbose and need the extra real estate without having to resize the edit window every time i use it.
I see, thanks. Sorry I didn’t report that issue because I assumed it was just a usability thing, but yours sounds like a valid usage case.
So I understand that you start with a blank reply, quote something, minimize the editor, select and quote something else, maximize the editor, and the first quote is gone?
Yeah it goes all wonky with that reload/ignore error
1 Thank
Never underestimate a web browser’s ability to use all available resources. 
But seriously, getting an accurate scrollbar involves a few things:
- Fetch all posts in the thread. This sends a whole bunch of requests to the server, increasing load and hosting costs.
- Render each post, to find out how much visual space it takes. This may result in an extremely large page canvas, like 1920 pixels wide by a million pixels tall. For a thread with 1000 posts, that could easily exceed the browser’s maximum memory limit per process. For a 10,000 post mega-thread, the canvas alone could exceed the total RAM on the entire computer.
- Once the above is done, an accurate scrollbar can be presented.
Even on old BLF, with just 30 posts per page, sometimes the canvas would exceed the limit the browser used for some functions. Like, there was a full-page screenshot tool, but the browser wouldn’t allow it to save images larger than 32768 pixels tall. And some pages, at 30 posts per page, exceeded that limit.
If accuracy isn’t as strict though, more efficient solutions could be used. Like, fetch only a few posts, and estimate the size of everything else without loading or rendering anything. Not sure how feasible this is, but it could theoretically work. That’s what Discourse’s timeline slider does, but I don’t know if it can be implemented at a browser level.
Or, if the goal is to reach the first or last post quickly, there are other, much simpler solutions:
- Press the Home or End key. Discourse uses these to jump to the first or last post.
- Click the begin or end date in the timeline widget. This works on mobile, where there are no keys to press.
These work pretty well. It’s like clicking the “first page” or “last page” buttons on the old site, except now there’s a hotkey for it.
1 Thank