W3C home > Mailing lists > Public > public-html@w3.org > December 2010

[Bug 11548] New: Suggestion for improved caching functionality in html5 specification

From: <bugzilla@jessica.w3.org>
Date: Tue, 14 Dec 2010 13:22:50 +0000
To: public-html@w3.org
Message-ID: <bug-11548-2495@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11548

           Summary: Suggestion for improved caching functionality in html5
                    specification
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: HTML5 spec (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: slgard@gmail.com
         QAContact: public-html-bugzilla@w3.org
                CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
                    public-html@w3.org


Sorry to bother you. I've never attempted to contribute to the html
specification before, so I'm not sure I'm going about this the right way?

I'm in the process of developing a html5 app and have run into a problem that I
think seriously threatens the usefulness of html5 as a platform for building
applications.

Essentially, the lack of an api call along the lines of .add_to_cache(url,
expires) seems like a glaring omission and means that I can't (for example)
have some javascript dynamically generate links to images and have those images
cached locally.

Here is a link to a question from someone else having the same problem
http://stackoverflow.com/questions/3476864/html5-iphone-dynamic-caching-of-images
There seem to be many people with similar issues.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Tuesday, 14 December 2010 13:22:53 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:07 UTC