This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 22640 - CryptoOperation.abort() returns a useless CryptoOperation
Summary: CryptoOperation.abort() returns a useless CryptoOperation
Status: RESOLVED WONTFIX
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-10 20:33 UTC by Eric Roman
Modified: 2013-07-18 23:28 UTC (History)
1 user (show)

See Also:


Attachments

Description Eric Roman 2013-07-10 20:33:08 UTC
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.
Comment 1 David Dahl 2013-07-10 20:57:00 UTC
(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"?
Comment 2 Eric Roman 2013-07-10 21:08:00 UTC
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.