- From: <bugzilla@jessica.w3.org>
- Date: Fri, 26 Sep 2014 16:18:29 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26301 Boris Zbarsky <bzbarsky@mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Normalization: Should |Normalization: Should throw |through instead of |instead of returning an |returning an Error instance |Error instance --- Comment #5 from Boris Zbarsky <bzbarsky@mit.edu> --- > I understood comment 1 to be questioning whether 'throw an <object>' was > well-defined when invoked from sub-algorithms. I see. A bunch of things regarding exceptions are fairly fuzzy. But the only sane interpretation of "throw" is that you terminate execution of the algorithm and all ancestor algorithms until you get to one that says it catches exceptions. There are complications involved when calling back into JS if _that_ throws an exception; that's what the rethrowing bits in DOM are about, because the call back into JS effectively catches exceptions that JS throws. But you're not in that situation here. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Friday, 26 September 2014 16:18:30 UTC