<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>9339</bug_id>
          
          <creation_ts>2010-03-26 15:17:37 +0000</creation_ts>
          <short_desc>&quot; Until the manifest is changed, those pages will not be fetched from the server again.&quot; WHAAAA? In order to get the benefits of app cached images and scripts and css, I have to have HTML pages that are never updated with fresh info, except when I change</short_desc>
          <delta_ts>2010-10-04 14:28:19 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>HTML WG</product>
          <component>pre-LC1 HTML5 spec (editor: Ian Hickson)</component>
          <version>unspecified</version>
          <rep_platform>Other</rep_platform>
          <op_sys>other</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>NEEDSINFO</resolution>
          
          
          <bug_file_loc>http://www.whatwg.org/specs/web-apps/current-work/#a-sample-manifest</bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P3</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>LC</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>contributor</reporter>
          <assigned_to name="Ian &apos;Hixie&apos; Hickson">ian</assigned_to>
          <cc>ian</cc>
    
    <cc>mike</cc>
    
    <cc>public-html-admin</cc>
    
    <cc>public-html-wg-issue-tracking</cc>
          
          <qa_contact name="HTML WG Bugzilla archive list">public-html-bugzilla</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>33943</commentid>
    <comment_count>0</comment_count>
    <who name="">contributor</who>
    <bug_when>2010-03-26 15:17:37 +0000</bug_when>
    <thetext>Section: http://www.whatwg.org/specs/web-apps/current-work/#a-sample-manifest

Comment:
&quot; Until the manifest is changed, those pages will not be fetched from the
server again.&quot; WHAAAA? In order to get the benefits of app cached images and
scripts and css, I have to have HTML pages that are never updated with fresh
info, except when I change the manifest, and then everything is updated?
That&apos;s just crazy!!

Posted from: 67.188.133.45</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>34383</commentid>
    <comment_count>1</comment_count>
    <who name="Ian &apos;Hixie&apos; Hickson">ian</who>
    <bug_when>2010-04-02 06:10:34 +0000</bug_when>
    <thetext>EDITOR&apos;S RESPONSE: This is an Editor&apos;s Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Did Not Understand Request
Change Description: no spec change
Rationale: I don&apos;t understand. Could you elaborate? The offline application cache mechanism is intended for caching offline applications, where the dynamic data is data, not in the HTML. If all you want is to benefit from caching of common resources, you don&apos;t need this, just use HTTP caching.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>