Purpose...
Builds...
Latest Build...
Mini-Help...
Full Help...

https://webprog3.com/purpose,sametab

https://webprog3.com/builds,sametab

https://webprog3.com/latest,newtab

https://webprog3.com/mini-help,sametab

https://webprog3.com/help,sametab

https://webprog3.com,sametab

Browser Cache
Open up the menu and select Preferences.
In the following window, choose Privacy & Security.
Personally, I prefer to leave cookies and site data intact.
Just click on "Clear" and you are done.
Some people actually clear out the browser cache as a matter of routine on a regular basis, say once a day.
Perhaps that's not a bad idea.
Be a bit careful here, because both options are selected by default.
If you scroll down, you will see "Cookies and Site Data".
Click on the "Clear Data..." button.
The cache is where the browser stores images, webpage scripts, passwords, and other data that have been downloaded from the same source on previous occasions. This is so that such items can be used immediately instead of waiting for them to be downloaded again. So for example, if you are developing and perhaps debugging a particular script, making changes and saving as you go along, every time you navigate to it you will get the old version instead of the new one! Every time you need to clear out the cache and re-load the script! Quite frankly, the browser cache can be a pain in the a..........rm.
That's not all. On (fortunately infrequent) occasions, your browser can become totally confused, seemingly unable to do anything right, and when this happens I am sure it is the rubbish in the cache that is at the bottom of it. It can also be that management of WebStorage also gets in a tizzy. I think that the browser cache is really a relic of the past, when Internet speeds were much slower and capacity (space) was far more limited. Of course, supporters of the cache's existence (the browser manufacturers), particularly the part of it for storing images, will defend their decision to keep it by lecturing me about having to respect available bandwidth, the public's need for speed, and so on. But it is unlikely that I would ever be convinced by such arguments. In my experience, the use of a browser cache (at least for images) seems to be more trouble than it is worth nowadays, and I look forward, if I live long enough, to seeing a cacheless world.
Wow! I began this section with a rant. Sorry about that. Now down to business.
First, let me make it clear that what I said about old versions of scripts etc. being presented by the browser applies only to when your script is being run independently, perhaps up on the Internet or on a local server, and you repeatedly navigate to it. But as you are developing and testing your web page in webProg3, none of this will happen in relation to your script. If anything unexpected happens, it will be in relation to WP3 itself. And only then (normally) if you really push it to the limit by giving it gigantic images or excessively long pages for example. So what are the limits of image size and page length? Well, that's the rub. It is difficult to say really. All you can do is find out the hard way, as I did with the preparation of this Help. In the case of a few very long pages, the browser went on strike and I was forced to separate them into two smaller halves. Fortunately, the workaround was simple. When the halves were ready, I just manually copied the HTML widgets from the second half back into the first one, and bingo. It seems that when you run a script in the browser outside WP3, there is little or no limit on how long or fat your script can be.
If ever things stop working properly, and you are forced to do something about it, try to clear down LocalStorage first if you can. This might even get things running again immediately, without your having to re-load anything. Of course, you can only do this if WP3 is open and you are able to click on the LocalStorage icon at the top of the screen on the extreme right. If you are temporarily unable to run WP3, wait until you get it up and running again, and then clear LocalStorage. (Theoretically, this should never be necessary because WP3 itself clears LocalStorage for the domain immediately when it starts up. However, for reasons that are not clear, a manual cleardown of WebStorage on the part of the user can sometimes help.)
Regarding the potential problems of LocalStorage capacity described above, there is a workaround.
Click HERE for full details.
Next, clear the browser's cache. Here's how you do it.