Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Must press F5 for every page you go onto in order for the autoblockrefresh setting to take affect

  • 8 replies
  • 1 has this problem
  • 1 view
  • Last reply by cor-el

more options

Why is it that now with firefox, I must press F5 each and every time I go to a different page to have the autoblockrefresh option to take effect?

Why is it that now with firefox, I must press F5 each and every time I go to a different page to have the autoblockrefresh option to take effect?

All Replies (8)

more options

Hello dodgester,

There used to be a setting in Options, but that was quite a few Firefox versions ago - there now is a preference on the "about:config" page :

Type in the address bar about:config (press Enter) (promise to be careful, if asked)

Type in the search bar and look for the preference :

accessibility.blockautorefresh :

its value needs to be set to false to turn it OFF

its value needs to be set to true to turn it ON

(after a value has been changed : close and restart Firefox)

more options

This option has been turn on for quite some time and it still does not stop the auto refreshing of pages that does automatic refreshing. Even with having restarted the computer (that obviously is more than just closing out the browser and reopening), it still doesn't stop the autorefresh of pages. The only way I been able to get these pages to stop autorefresh is not to only have this option turned on (true), but also to have to press F5 key each and every time I go onto a such page that has autorefresh taking place.

more options

Can you attach a screenshot?

more options

When you asked for a snapshot, the only thing I could think you may be referring to is the setting. How can you get a snapshot of a page auto-refreshing otherwise when that requires videoing it.

But then finding undocumented bugs is nothing new to me as I have been doing it for years including when Excel 97, SR2 had the following errors that got MS to send me Office 2000 free of charge as a fix to the below bugs:

1) A sum of more than 25 cells divided by a sum of more than 25 cells gave the result of "1/0"

2) No matter what settings were put on the legends of the charts within Excel, through the process of updating the numbers, that then updated the graphs, printed the charts, and saving the file all via a single macro, the legend would gradually work it's way to be in the top center position of the chart area.

3) Exceed more than 65,536 defined names within a single workbook and saved it as such, then close it out; the next time you open the workbook, everything except for data values and formulas would be removed from the workbook. Not only that, but if the workbook had more than 32,767 defined names, some of the properties within the workbook may not work properly. This issue persisted through Excel 2003.

These were just three of the bugs of Excel 97, SR2. There were so many bugs within Excel 97, SR2 I had to deal with, I hated using that version and service pack. I would have rather used Lotus 1-2-3, v2.3 (yep, that's the old DOS version prior to it going to Windows with v3.0), than to use Excel 97, SR2. Just most people didn't notice the bugs because most people barely even scratch the surface of Excel. Excel 2000 fixed many of the bugs, and as a bonus for just upgrading from Excel 97 to Excel 2000 without any modifications to my VBA codes, it only to Excel 2000 1/3 of the time it took Excel 97 to process the macros with the calculation mode set to manual in both cases.

As a general rule for me, which I have applied ever since grade school years, if something is proven to not work properly, I have a very high tendency to steer completely away from it (unless I have no realistic choice but to have to deal with it) and find other work arounds until it is otherwise proven to be fixed. I been doing programming work ever since 7th grade when I was first introduced to computers on the programming side (BASIC programming language, that had line numbers) at a time when there were no mouse to use with the keyboard. Yes, not a normal way to introduce someone to computers, and while my teacher didn't intend on teaching me programming, I picked up on it just by picking up on the patterns that I saw in the coding she had me type into the editor. She was only attempting to help me out with my spelling and thought to try that not knowing if I would even pick up on it let alone how far I would take it.

This is one of those cases that I more or less have to deal with the issue for the following reasons:

Google Chrome has broken the autorefresh blocker add-in

Edge, forget it as I have had to deal with way too many security issues right from the start.

IE hasn't been as trustworthy to use as it is now a dead interface given MS is now focusing onEdge, but way too much stuff started popping up right from the start of using Edge, causing a lot of issues. As such, Edge is essentially on the black list.

more options

If block refresh is active then Firefox will show a notification bar at the top of the page. This only works in cases where a META tag is used to redirect you.

Keep in mind that block auto-refresh is meant as an accessibility feature for people who use a screen reader.

more options

Maybe so, but it used to work properly, but not anymore. I don't like it when a page is refreshing on me every 5 to 15 seconds and taking it back to the top of the page as I am attempting to read it. That is so very annoying.

more options

dodgester said

Maybe so, but it used to work properly, but not anymore. I don't like it when a page is refreshing on me every 5 to 15 seconds and taking it back to the top of the page as I am attempting to read it. That is so very annoying.

It wouldn't make any sense for a site to refresh a page that frequently during normal use. So something must not have been normal as far as the page was concerned.

If reloading the page using F5 calms it down, that could indicate Firefox was using one or more cached files with obsolete/invalid content and some script in the page was trying to work around that over and over.

Corrupted cache maybe? You could try clearing it and see whether that helps: How to clear the Firefox cache.

more options

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.

  • switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Safe Mode start window