Safari favicon not updating

HTML5 addresses some of the annoyances of being offline with the Application Cache interface.

To enable the application cache for an app, include the manifest attribute on the document's will be implicitly added to the application cache. If they link to the manifest, they will all be implicitly cached separately.

Thus, there's no need to list every page in your manifest. Because of this and other gotchas, App Cache best used on apps with one URL.

If a page points to a manifest, there's no way to prevent this page being cached. You can see the urls that are controlled by the application cache by visiting chrome://appcache-internals/ in Chrome.

Hi, I went and replaced in template/it_smartshop/ but the site still uses the default joomla icon.

In the recent slew of updates brought by OS X Yosemite 10.10.3, which included a new Photos app and more than 300 new emoji, one tiny but very important fix is easily overlooked: Safari no longer saves website favicon URLs while in Private Browsing mode.

Until now, even if you were browsing privately in Safari — which should leave absolutely no traces of your browsing history — Safari kept records of all the favicons from the sites you visited.The favicon is the tiny icon that sometimes appears in front of an URL field in your web browser, and it's mostly a cosmetic feature.However, knowing which site it came from is very often the same as knowing which sites you were browsing, rendering the entire private browsing session very vulnerable to someone who knows where to look. Until now, the only way to fix it was to delete the entire portion of Safari's database that collects favicons.Apple does not go into details about the fix; a single sentence from the latest Yosemite release notes claims the update "prevents Safari from saving website favicon URLs used in Private Browsing." Private browsing is also available in Chrome (where it's called Incognito mode), Internet Explorer (where it's called In Private Browsing) as well as Firefox.It's becoming increasingly important for web-based applications to be accessible offline.Yes, all browsers can cache pages and resources for long periods if told to do so, but the browser can kick individual items out of the cache at any point to make room for other things.