- From: <bugzilla@jessica.w3.org>
- Date: Wed, 07 May 2014 15:48:33 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25343 --- Comment #12 from Arun <arun@mozilla.com> --- (In reply to Simon Pieters from comment #11) > I don't really object to exposing it, but it hasn't been backed by a > convincing use case IMHO. > > It seems you added it to the spec already. I feel strongly that it should be there. I agree that the loss of reference / null argument is a good workaround to the previous use case, but that is semantically and functionally different from .close(). I'll remove it if it's demonstrably harmful or if all implementers determine it is redundant. > > You shouldn't both say that isClosed returns true/false depending on > readability state *and* set isClosed to true/false in other algorithms when > setting the readability state (in slice(), close(), new File(), new Blob()). > Do one or the other. OK, done: new Blob(): http://dev.w3.org/2006/webapi/FileAPI/#constructorBlob slice(): http://dev.w3.org/2006/webapi/FileAPI/#slice-method-algo close(): http://dev.w3.org/2006/webapi/FileAPI/#close-method new File(): http://dev.w3.org/2006/webapi/FileAPI/#file-constructor -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 7 May 2014 15:48:34 UTC