Naveen, thanks for the fast response. No solution yet, but I've got some leads as a result of more breadcrumbs found by researching your post.
I already had that "Warn me when web sites try..." option checked. It does not work.
Other users also report it doesn't work. Apparently the damned website programmers code a way around that restrictions. Just to be sure, I also verified that the "Warn me when web sites try..." associated 'about:config' parameter was properly set to "True":
"Checking the option is equivalent to setting accessibility.blockautorefresh
preference setting in 'about:config' to True
In reading one of those articles, another user suggested using Firefox's "about:config" to modify another parameter as follows:
Eli December 20, 2010 at 9:29 am
That also doesn't affect the auto-refresh activity on those accursed websites.
Type.. about:config.. in your address bar and type "frequency" in the filter and double-click on browser.cache.check_doc_frequency. Use a value of 0 (check doc once when you first visit) or 1 (check everytime you revisit). Do not use 2 (never check, only use cached copy). Default is 3 (check at some pre-determined intervals). Browser scripts can over-ride this though.
What amazes me is that none
of the 4 search engines I tried (including searching within the Mozilla "add-ons" site) pointed to any of these possible solutions, and I was using keywords like "block refresh", "block auto-refresh", and similar. Now I've got to wonder if the search engines intentionally lowered the priority of presenting these solutions...which would indicate they're attached to the cabal that supports this user unfriendly auto-refresh crap. Get my tin-foil hat ready.
Note: as I postulated, it appears many others agree the reason for auto-refresh IS to artificially increase "page-hit" statistics. The deep and personalized resentment expressed by other users toward this highly intrusive tactic is apparent.
See this for more info on that: http://www.hardwarecanucks.com/news/web-business/dark-side-web...inflation/
And now...as seems always inevitable in these kinds of things...it gets messy.
In one of the thread however, there is a post that indirectly points to a mozilla add-on (which my searches within the Mozilla add-ons website also did not reveal). I am going to try this add-on if I can, and report back. I hope that it actually actively intercepts the code and it is not a stupid utility that just sets the above discussed parameters.
However, there is another post that says that add-on won't work and which led me down a screwy path pointing to https://www.userscripts.org/scripts/show/35375
which seems to have been reborn as http://userscripts.org/,
and I searched for the referenced "userscript" 35375. That userscript wasn't found but the search did produce this page pointing to yet two more "userscript" auto-refresh blockers:
which points to