We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

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

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Firefox only uses old non-existing Javascript file, and will not access the newer edited file

  • 3 uphendule
  • 1 inale nkinga
  • 1 view
  • Igcine ukuphendulwa ngu cor-el

more options

Win10 and Firefox (89, and 90 does not correct it) is only running an older no-longer-existing version of my javascript file (from the html web file). It does not access the new edited javascript file with same file name. Sounds impossible, but I have edited the javascript file (including added an alert to change the modified date again), but Both the debugger and the regular direct URL continue to run the older script file (the new alert does not trigger, and the older code is directly visible in debugger, which does not match new file that exists). Firefox will not access the new edited javascript file. It always worked fine until this week, but not now. This old file that runs does not exist on my computer, except obviously in some Firefox cache. I have cleared cache, and disabled Cache in the Firefox Network tab, with no effect. It is a shutdown situation now. To continue using Firefox, how can I bypass this bug to be able to access and use the edited Javascript file? I've used Firefox and Javascript a few years, and never saw this before.

Win10 and Firefox (89, and 90 does not correct it) is only running an older no-longer-existing version of my javascript file (from the html web file). It does not access the new edited javascript file with same file name. Sounds impossible, but I have edited the javascript file (including added an alert to change the modified date again), but Both the debugger and the regular direct URL continue to run the older script file (the new alert does not trigger, and the older code is directly visible in debugger, which does not match new file that exists). Firefox will not access the new edited javascript file. It always worked fine until this week, but not now. This old file that runs does not exist on my computer, except obviously in some Firefox cache. I have cleared cache, and disabled Cache in the Firefox Network tab, with no effect. It is a shutdown situation now. To continue using Firefox, how can I bypass this bug to be able to access and use the edited Javascript file? I've used Firefox and Javascript a few years, and never saw this before.

All Replies (3)

more options

Oops! I am the OP, and switching to Chrome to try to continue working, I discover Chrome (which has NOT been used with the debugger before) has the same problem with exactly same symptoms. Same HTML file which includes the same javascript file name, which has since been edited, but instead it gets an older version no longer existing. I have no clue, other than I must be trapped somewhere in science fiction. Guessing it must be Windows 10 issue somehow. Win10 was updated to version 21H1 yesterday, when the problem was first noticed.

Sorry.

more options

You can reload webpage(s) and bypass the cache to refresh possibly outdated or corrupted files.

  • hold down the Shift key and left-click the Reload button
  • press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
  • press "Command + Shift + R" (Mac)
more options

Note that you can add a get parameter to the link with some random code or a timestamp to make the link unique to avoid such update a file.