- TODO: there are console.logs that still need to be removed
- Posting was loading the new page twice - once in ajax.js and once in
auto-reload.js. auto-reload will handle this behaviour, the other is
commented out
- The new post does not immediately show up when immediately ajax
requesting the page after posting completes. Adding an epoch query
parameter did not change this. Instead of figuring out why it was easier
to add a 500ms delay before requesting the page, now it seems to work
well.
Executing a function to make a get request while simultaneously triggering a scroll event within the executed scroll event is probably not the best idea.
This still needs work, there should probably be something else used to check for updates, such as an event where page has focus or something else that doesn't get called so many times, preferably something that reduces the timer instead.
This is just a quick fix to stop all the lag on threads when scrolling near the bottom.
Fixed an issue with the scroll hook thread polling.
Users scrolling near the bottom of the page are making upwards of 7-10 requests a second to the site.
Added a small timer using the "poll_interval_mindelay" value to prevent unnecessary polling, one is enough during this minimum time delay.
check if viewing a thread or viewing a board page when updating a thread so new posts do not appear at bottom of page while viewing threads list not sure if this was because of an outdated template but I thought I should point out this as it may affect html templates no matter the code as the banner code is the only code that checks where the user currently is.
discomrade
towards-a-new-leftypol
nonmakina
Benjamin Southall
Simon McFarlane
Michael Walker
czaks
ScriptKi77y
Bui
topkek
8chan
undido
Michael Save