- From: <bugzilla@jessica.w3.org>
- Date: Wed, 15 Dec 2010 00:48:00 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11548
Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bhawkeslewis@googlemail.com
--- Comment #3 from Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com> 2010-12-15 00:47:59 UTC ---
(In reply to comment #2)
> yes, but then caching policy is controlled purely by the cache header sent by
> the server?
>
> If that's a server I don't control -in this specific case twitter.com- there
> doesn't seem to be anything I can do about the lack of caching.
That's probably a feature not a bug.
> I wouldn't dream of a change to the html spec to solve my specific problem with
> a specific website :) but it just seems that javascript ought to have the
> ability to dynamically change what gets cached within it's domain?
What do you mean by "it's domain", and why should it have that ability?
Anyhow, if you really want to preserve image state without reference to the
original resource, load it into a canvas bitmap and persist that.
--
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 Wednesday, 15 December 2010 00:48:01 UTC