I need to modify the hash, remove it after certain processing takes place so that if the user refreshes they do not cause the process to run again.
This works fine
Here is a cross-browser solutions. Works in IE, Chrome, Safari, and FF (tried with latest versions).
var pos = location.href.indexOf('c=');
location = (pos < 0 ?
location + (location.href.indexOf('?') < 0 ? '?' : '&')
: location.href.substring(0, pos))
+ 'c=' + Math.floor(Math.random()*11) + '#' + comment_id ;
Basically, I leverage query ("?") string to trigger the page reload with hash. What the first line does is it checkes whether there is our "golden" query string (I use "c" variable which stands for "comment"). If there is,
If there is no,
The reason I add a random number after "?" is that after the first reload there is something like "?#comment-10". In this case, the next change to the URL will not reload the page, since browser understands it as an anchor jump instruction.
To force reload, we need to add some random thing to the query so that the new URL is different from the previous.
This solution will work on all browsers and will make sure the reload doesn't break the existing query. The only note is to make sure your "golden" query variable name is unique.
Hope this helps.