Software Update [OCT/2017]

[stryder]

Unfortunately the centering side effect is caused by a change in part of the "guest" template (I altered it slightly to move the google search bar to below the navigation bar). I might well debug it in time.

I was/am trying to make the forums a little more mobile friendly, currently though it's still awkward. I'm not much for mobiles, someone gave me an old Iphone 5c that I can look at the pages though (It doesn't render particular well when the phone is vertical, although the website is viewable horizontally.) I'll keep chipping away at implementing some changes, to see what does or doesn't fit. (You might also notice that the site now occupies the full browser screen rather than a large border either side. This means to get the optimum view size, adjusting the browser windows size is advised.)

[stryder]

Incidentally, if you find the website sluggish today there is a likelihood that the host is having a problem with one of it's other clients eating all the process time up on the servers.  I'll see what I can do about getting it fixed.

---

Thanks Stryder.  I noticed that the reversion to page top and scrolling problem seem to be gone when I turn off the data saver on Chrome.

Another thing I noticed was when I tried to go directly to page 3 in this thread, the wait arrow would just keep spinning.

I saw the scroll bug on a Chrome browser today, what seemed to happen was that when a page populated with a lot of data was loaded (in this particular instance it was an image search on google) scrolling down the page of images resulted in the occasional pause and then the scrolling moving back up slightly before being able to continue to scroll down (via mouse wheel). It appears to be that the Chrome browser has a limit to how much data it will cache before it requires pulling more data, at this point that's where the scroll issue seemed to occur. I'm not sure if it was exactly the same problem as you had or not.

I think the reason I didn't see it previously on my own copy of chrome is I tend to use Incognito browser sessions (well, the browser set to clear all caches everytime they close). The bug would likely be seen if I'd saved data, passwords, autofill data etc

I actually spotted this when dealing with a different Chrome bug involving website translations through Google. Apparently if you save a lot of data to be remembered it can actually effect the browser capacity to translate pages (It gives a 400 error when you attempt to translate). The fix was to actually clear the cache.