This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
CryptoOperation.abort() returns itself. As currently described, i don't think this is very useful. It wouldn't make sense for the consumer to chain using this Promise, since by definition it is is trivially rejected. Moreover, the promise does NOT indicate when abort() has actually completed (in case the implementation takes a while to cancel the underlying operation). I propose making the return type of abort() be void.
(In reply to comment #0) > CryptoOperation.abort() returns itself. > > As currently described, i don't think this is very useful. > > It wouldn't make sense for the consumer to chain using this Promise, since > by definition it is is trivially rejected. I would think the user might want to introspect the properties of this promise on abort(), no? > > Moreover, the promise does NOT indicate when abort() has actually completed > (in case the implementation takes a while to cancel the underlying > operation). > > I propose making the return type of abort() be void. Doesn't this break the "Promises model"?
Thanks David. I suppose introspection could still be useful. Feel free to close this as a "won't fix" if you think the current model makes sense.