- From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
- Date: Tue, 15 Sep 2009 06:36:32 +0000
- To: public-html-commits@w3.org
Update of /sources/public/html5/spec In directory hutz:/tmp/cvs-serv21963 Modified Files: Overview.html Log Message: appcache intro: Mention that the main page is always cached. (whatwg r3855) Index: Overview.html =================================================================== RCS file: /sources/public/html5/spec/Overview.html,v retrieving revision 1.3021 retrieving revision 1.3022 diff -u -d -r1.3021 -r1.3022 --- Overview.html 15 Sep 2009 05:27:24 -0000 1.3021 +++ Overview.html 15 Sep 2009 06:36:29 -0000 1.3022 @@ -46450,7 +46450,10 @@ <p>The time is: <output id="clock"></output></p> </body> </html></pre><p>Now, if the user goes to the page, the browser will cache the - files and make them available even when the user is offline.<h5 id="event-summary"><span class="secno">6.9.1.1 </span>Event summary</h5><p><i>This section is non-normative.</i><p>When the user visits a page that declares a manifest, the browser + files and make them available even when the user is offline.<p class="note">Authors are encouraged to include the main page in + the manifest also, but in practice the page that referenced the + manifest is automatically cached even if it isn't explicitly + mentioned.<h5 id="event-summary"><span class="secno">6.9.1.1 </span>Event summary</h5><p><i>This section is non-normative.</i><p>When the user visits a page that declares a manifest, the browser will try to update the cache. It does this by fetching a copy of the manifest and, if the manifest has changed since the user agent last saw it, redownloading all the resources it mentions and caching them
Received on Tuesday, 15 September 2009 06:36:42 UTC