- From: <bugzilla@jessica.w3.org>
- Date: Fri, 11 Nov 2011 23:40:27 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14702 --- Comment #12 from Yehuda Katz <wycats@gmail.com> 2011-11-11 23:40:26 UTC --- Let me try to articulate the use-case clearly. A web author has a web site, say a blog, with significant static content, but which is regularly updated. He develops this web site using HTML, and updates it routinely as desired. Many of the readers of his site would like the ability to read this content reliably offline, but he would also like to make sure that any new content is available immediately. He does not know JavaScript, so he cannot notify the user that new content has become available using the applicationCache API. Alternately, he does not want to interrupt his users from reading content when the application cache is updated in the background. At present, in order to make his content available offline in a reliable way, he must use the application cache. However, once he has done so, his users will always receive the last version of his content, even if they are online. To avoid this problem, he can use JavaScript to notify the user that the site has new content, but he may not know enough JavaScript to achieve this, and even if he does, it produces a degraded user experience. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 11 November 2011 23:40:28 UTC