- From: Ian Hickson <ian@hixie.ch>
- Date: Tue, 21 Dec 2010 21:05:14 +0000 (UTC)
- To: Arun Ranganathan <arun@mozilla.com>
- cc: Michael Nordman <michaeln@google.com>, Jian Li <jianli@chromium.org>, Eric Uhrhane <ericu@google.com>, Web Applications Working Group WG <public-webapps@w3.org>
On Tue, 21 Dec 2010, Arun Ranganathan wrote:
>
> I've bolstered the lifetime conformance language with this:
> http://dev.w3.org/2006/webapi/FileAPI/#lifeTime
Just one minor nit, the "unloading document cleanup steps" get called both
when "unloading" a document and when "discarding" a document, and may in
the future be called in other situations also, so it's best to just say
something like "This specification defines the following unloading
document cleanup step: ..." rather than using the imperative ("as part of
the unloading document cleanup steps, user agents must...").
(Another way to think about this is that there should really only be one
"MUST" for each requirement, and there is already one that triggers the
cleanup steps. You only want one "MUST" per requirement otherwise you end
up with situations where you might have to technically do the same thing
multiple times in order to fully comply with all the requirements.)
> The only nagging doubt I have about this proposal is that the creation
> and revocation methods (static) are on window.URL, but the actual Blob
> object has an affiliated document, which upon cleanup flushes the URLs
> affiliated with it.
Window and Document objects have an almost 1:1 relationship. There is one
edge case exception involving about:blank, but I don't think it causes an
issue here.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 21 December 2010 21:05:43 UTC