[Bug 25343] Expose an isClosed property on Blob Objects

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25343

Simon Pieters <simonp@opera.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simonp@opera.com

--- Comment #8 from Simon Pieters <simonp@opera.com> ---
(In reply to Arun from comment #6)
> I'd like other use cases, too, but I think it's useful to have.

This seems backwards. :-) You don't start with a solution and then try to think
of cases where it would be useful. You start with a problem and then try to
come up with solutions that solve the problem.

In the game scenario with textures, the use case is adequately handled by
losing the reference to the blob, as Glenn pointed out.

Are there other use cases?

It's hard to evaluate whether the property makes sense without understanding
how it would be used. For instance, I don't see why it shouldn't be exposed as
a .readable property with inverted semantics, so that if you want to check it
before reading a blob, you can use it directly in an `if` without flipping the
value.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 6 May 2014 07:58:36 UTC