Having trouble with hard page refresh in Firefox/MacOS - macos

I made some alterations to a page, and, using Firefox, did a Shift-Command-R to hard reload it. When I do that, Firefox reloads the new page as expected, but if I then do an ordinary page reload (e.g. Command-R) reloads the old version of the page.
I don't get this behavior using Chrome; I only have to do the hard page reload once, and the new version loads from then on with an ordinary page reload. So it doesn't look like this has anything to do with my hosting service (BlueHost).
I've tried:
Clearing the cache, using Firefox/Preferences/Advanced/Network and hitting the "Clear Now" button in the "Cached Web Content" area.
Deleting all cookies associated with the site containing the page.
Quitting Firefox and opening it again.
After doing all of these, I still get the same behavior: Shift-Command-R loads the new version of the page, and Command-R loads the old one.
Firefox version is 52.9.0; MacOS version is 10.13.6.
Can anyone shed some light on why this is happening?

This behavior is by design in FireFox:
Reload F5 (or) command + R
// does not override cache
Reload (override cache) command + shift +
R
// override cache
↳ Keyboard shortcuts - Perform common Firefox tasks quickly

Related

airconsole simulator isn't showing my updated code when refreshed

I'm trying to test my game on the site using the simulator page. however I'm running into a problem. no mater what it seems like my page updates are not changing on the simulator. I've tested locally on the pages, and they work fine.
anyone know? i haven't seen anything in documentation
At least for me when I'm testing the controllers for the Unity project, or another HTML / Javascript project I need to clear the cache once in a while to make it work.
For Firefox; Options (top right corner) - Privacy & Security (left menu) - Clear data (button on the right)
(I untick the "Cookies and Site Data" because it does not affect to this problem.)
And just to make it clear, it's not an AirConsole problem. If you have ever tried to create a local website and you are testing stuff this might happen as well. Also, you don't have to do this everytime something changes.
Just found out that if you add something a question mark after the address and put something random after it, it will refresh well again (a bit like what is done in web with images to avoid caching sometimes).
Example:
Original url: http://www.airconsole.com/#http://192.168.1.2/game
Url after 1st change: http://www.airconsole.com/#http://192.168.1.2/game?1
Url after 2nd change: Url after change: http://www.airconsole.com/#http://192.168.1.2/game?2
etc...
UPDATE
I've also found that the following works:
Original url: http://www.airconsole.com/#http://192.168.1.2/game
Open a tab with http://192.168.1.2/game/screen.html
Do CMD + Shift + R on OSX or Ctrl + F5 on Windows when using Chrome
Switch to the original airconsole URL tab and do the previous step
Your game is now refreshed

Lock Firebug to a specified page

Is there a way to keep Firebug on a single page, so that when I switch pages it remains on the page I want it set to?
For example, I'm working on a project and I get an error that I want to search for on Stack Overflow, but when I navigate here, the console changes to reflect this site. I'd like to stop that from happening.
There is no option to "pin" a page's data in Firebug (as of version 2.x). As far as I know this also doesn't work in any of the browser built-in dev tools.
Though the simple solution for your problem is to open the other page in a separate tab or window. Doing so keeps all the data of the page saved when you switch back to the tab containing your project's page.
Note that Firebug's activation model is based on URLs following the same origin policy. I.e. if you open it for your project's page, it will always get opened for your projects page, even on other tabs, but not for any other site.
I've found it useful to split the tab of interest off into a new window and to activate Firebug on that window. That way I can continue using my original tab collection/window without it changing as I link-hop.

Is it possible to disable browser refreshing in Codekit 2?

Does anyone know of a way to disable browser refreshing in Codekit 2? I’m enjoying the local server feature, but we have multiple people working on the site, and every time one person changes and saves a file we all get our pages refreshed. I'd like to temporarily disable it.
I know there are other ways for folks to access my site locally, but Codekit is what we're using for this right now.
Simply pause file watching:
Press command + option + control + / to toggle CodeKit's file-watching
on and off.
This stopped auto refreshing for me when I made a change. You can still use codekit's address and it won't refresh when you make a change if you have paused watching.

Way to get Chrome to always re-download styles and images on every visit to the page during development/testing?

As brilliant as Firebug is, I would consider switching my JavaScript debugging to Chrome if I could figure out how to get it to always re-download styles and images on every visit to the page?
When I'm testing a page in Firefox, it always gets the latest version.
But in Chrome I often end up scratching my head over something that turns out to be a simple issue of the browser caching some earlier styles or images.
Is there a way to configure Chrome to cache less while you're developing?
I often use private browsing mode for this - it prevents caching of the stylesheets or scripts.
EDIT:
Another really easy way to do this in Chrome now is to go into the Chrome Developer Tools, click the settings gear (bottom right), and then check "Disable cache." See https://stackoverflow.com/a/7000899/4570.
A bit late to the party, but just for people who may pick up this page on a search, new versions of Chrome have a developers tools setting to disable the cache. Show developer tools (spanner->tools->developer tools) and on the bottom right is a tiny little gear. click that and a few settings appear in the developer tools window, one of which is to disable the browser cache. If you can't see it you may have to upgrade to a newer version of chrome.
Ian
According to Chrome help pages, Ctrl+F5, Shift+F5, Ctrl+R and Shift+R should force refresh. I haven't had problems with javascript and css but refreshing frames is another story. The caching can also be on your web server. The server can obviously be configured to cache css and javascript files.
Your best bet is to clear the cache between each load. With the latest version of Chrome, the hotkey is the same as firefox (on Mac, it's Shift-Command-Del). However, they haven't focused the "Clear Browsing Data" button, so you have to use your mouse to click that button -- which is a total PIA when compared to Firefox (Shift-Command-Del + Return), or Safari (Option-Command-E + Return).
the 2.5 ways i do it are not "automatic" but they're very quick, and i don't have to remember to switch back from private browsing -
a) install Mouse Gestures and use (this is a great extension anyways, but even more so now that I know about) Up, Down, Up - this is a cacheless reload. You can get it here
b) ctrl+shift+r is [supposed to be] a cacheless reload. Even the help pages admit this isn't perfect
c) the .5 is a kind of a hack - but if you are working with CSS files, open a new tab and type in the address to the CSS file itself - you can see what changes are there, as well as make sure that you've gotten the latest one by refreshing this file before your other file. a bit of a pain, i know, but always works.
Not sure about your system but on this WinXP machine holding SHIFT while clicking refresh always forces a complete download.
That's what I do when doing CSS and image tweaks.
That Chrome needs to have must-revalidate in the Cache-Control` header in order to re-check files to see if they need to be re-fetched the way that the other browsers do by default.
Recommend the following response header:
Cache-Control: must-validate
This tells Chrome to check with the server, and see if there is a newer file. IF there is a newer file, it will receive it in the response. If not, it will receive a 304 response, and the assurance that the one in the cache is up to date.
If you do NOT set this header, then in the absence of any other setting that invalidates the file, Chrome will never check with the server to see if there is a newer version.
Here is a blog post that discusses the issue further.

Cufon has a slight delay when refreshing BUT not when directly loading the page

I am using Cufon in Firefox, it has a slight delay of converting fonts to images when I F5 but not if I click on the URL bar and hit enter.
Any idea why? And it wasn't originally like this, I tried to add a line replacing another selector and then this happened. Then I undoed but the problem remains.
I assume this is because pressing F5 forces a reload of all attached scripts as well, which prolongs the time until the cufon replacement is processed (while the layout is already being rendered).
When entering a page normally, or reloading it by entering its URL again, the embedded scripts are not reloaded.

Resources