reference anchor instead javascript offset scrolling?

[ponzinomics]

I tried to post this question to the development forum but it seems I am not able to open threads on that board so I post it here instead.

When you click in the last thread of a board in the front page, it moves to the last post of the thread. Fine. The thing is that there is an URL which includes a javascript offset, as you can see here. It includes as URL arguments:

.....................?page=1#scrollTo=3078

I thing it would be smoother locating every post by a reference anchor, as it does not require any javascript. The problem that is causing me is that, on load, I also slide down a div, and there is an annoying up-down javascript scrolling.

Would it be nicer to add an empty anchor as <a href="#post_id"></a> on top of every post and move to this position by invoking:

ponzinomics.org/thread/612/brazil-monetary-policy-official-thread#post_id

You would not need a complicated offset (3078) calculation on serve side.

Thanks.

[Chris]

Each post already has an ID associated with it on the <TR id="post-nnnn"> element, so something like your url with an post ID on the end (e.g #post-1234) should work (without the need for a new anchor) and it used to work but that functionality was broken after an update and is on a list of bug fixes but not prioritized above more pressing matters. The Proboards software makes use of the url hash to pass parameters so on page load it grabs its own parameters then passes on yours to the browser. In this case however it is fumbling the hand-off and not getting back to the line of scrimmage.

[ponzinomics]

Ah, OK, makes sense. The anchor seems the obvious first choice as not javascript is required, but I understand about the temporary workaround because the bug.

A question that comes to my mind, are these kind of fixes transparent for us? I mean, some day in future can I expect that it will be automatically fixed or should I do anything when the core code gets fixed?

[Chris]

Keep an eye on the Development Blog for announcements regarding bug fixes and feature improvements or in this case you could periodically just test to see if the feature has been restored yet since all it requires is a hash at the end of the URL that leads to an element on the page with that specific ID or name.

Sorry for the late response btw.