html manifest attribute fixes: 1a)
1. Updating the cached resources WITHOUT modifying the Manifest file
a) users change the browser (or the pc) → the websites' updates display
Otherwise the website's updates WON'T display; tests:
- NOT Ok: re-accessing the page in a new tab
- NOT Ok: refreshing the page
- NOT Ok: closing /re-opening browser and re-accessing the page
Conclusion: if you update a cached resource without modifying the manifest file, one way of seeing the website updates is to change the Browser...but this is not a SOLUTION(video demo for example purpose)
Video demonstration html manifest attribute: Fixes 1a)
HTML5 manifest file Fixes, Tutorial
| min | video details |
|---|---|
| 00:02 | open browser |
| 00:06 | clear everything: cache, cookies... |
| 00:12 | accessing the about:cache page |
| 00:20 | Offline cache directory: empty |
| 00:25 | accessing an html file linked to a manifest file |
| 00:29 | Allowing resources storage for Offline use |
| 00:33 | refreshing about:cache page |
| 00:36 | accessing the List of Cache Entries |
| 00:47 | 5 resources have been cached: the html file which is linked to the manifest file (test.appcache) and the 3 resources listed inside manifest file |
| 00:51 | Note: main.css is a cached resource |
| 00:56 | we will update this cached resource by modifying the color of h1 (from blue to orange) |
| 01:12 | the cached resource, main.css, has been updated |
| 01:19 | re-uploading the cached resource, main.css, on Server The main question is: Will the user see the update ? |
| 01:27 | Test 1: re-accessing the page in a new tab Test result: NOT OK the cached resource, main.css, didn't get updated |
| 01:33 | Test 2: refreshing the page Test result: NOT OK the cached resource, main.css, didn't get updated |
| 01:37 | Test 3: closing and reopening the browser and reaccessing the page Test result: NOT OK the cached resource, main.css, didn't get updated |
| 01:49 | Test 4: changing the browser Test result: OK the cached resource, main.css, still didn't get updated in Firefox, while accessing it with a new browser, Google Chrome, first access, the last updates are cached and displayed |