This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Section "18.3. RSAES-PKCS1-v1_5" describes in fairly generic terms to "raise an error". It is ambiguous what raising an error means, given that it applies to both asynchronous and synchronous cases. In this case: "If key does not describe an RSA public key, raise an error and terminate the algorithm." I interpret "raise an error" to mean throwing an exception, since it is happening while initializing the CryptoOperation. However in the case 3.3, this same terminology is used in the context of finish(). Since the operation may not have completed yet (and hence the error is not known), throwing an exception does not make sense. The error would have to be delivered via the Promises reject() mechanism instead.
(In reply to comment #0) > Section "18.3. RSAES-PKCS1-v1_5" describes in fairly generic terms to "raise > an error". > > It is ambiguous what raising an error means, given that it applies to both > asynchronous and synchronous cases. > > In this case: > > "If key does not describe an RSA public key, raise an error and terminate > the algorithm." > Above the "raise and error" in section 18.3.4, there is an Ed. note: "Note: The following processing algorithms have not been updated to match the processing algorithm described in the CryptoOperation processing model." This section needs to be updated to match the Promises direction
All errors are now asynchronous according to Bug 24427.