- From: <bugzilla@jessica.w3.org>
- Date: Tue, 18 Mar 2014 12:51:22 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24576 --- Comment #12 from Simon Pieters <simonp@opera.com> --- (In reply to Arun from comment #9) > What should happen here IMHO is that if the read is underway, close() > shouldn't have an effect. Of course, subsequent async reads will fail. > > This should be made clearer. I don't think we can/should disrupt a read > that's underway. Do you agree? That sounds good to me. The spec seems clearer now than when I wrote the earlier comment, IIRC. > This should throw: > > var blob = new Blob(); blob.close(); URL.createObjectURL(blob); Why? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 18 March 2014 12:51:23 UTC