27305 2014-11-11 20:06:22 +0000 "Perform type mapping as specified in [WEBIDL] for data." 2016-05-23 22:47:25 +0000 1 1 1 Unclassified Web Cryptography Web Cryptography API Document unspecified PC All RESOLVED FIXED P2 normal --- 1 annevk sleevi bzbarsky public-webcrypto watsonm oldest_to_newest 114810 0 annevk 2014-11-11 20:06:22 +0000 IDL does this before the algorithm is invoked so there is no need to have this step anywhere. Also, the point where you try to perform it would lead to racing issues, as that part (potentially) runs in parallel with other JavaScript in the document. 114811 1 sleevi 2014-11-11 20:11:21 +0000 Could you provide clarification as to which instance you're talking about? I believe it's https://dvcs.w3.org/hg/webcrypto-api/raw-file/6694484cc545/spec/Overview.html#SubtleCrypto-method-wrapKey for jwk, but I wanted to make sure? I'm not sure the racing issues you describe, or why they'd be any different than http://heycam.github.io/webidl/#es-promise , but I guess if you can explain your concern in more detail, we can see what can be done. 114812 2 annevk 2014-11-11 20:31:28 +0000 I was looking at an outdated version of the draft that used it more frequently. The problem with converting a value late rather than at the boundary is that it can invoke JavaScript that runs in the scope of the page (ToObject, ToString, etc. have side effects). Now if you invoke JavaScript in parallel with other JavaScript, you've hit something that's undefined and will most likely crash. Anyway, there in step 14 /key/ will already have been converted due to it crossing the boundaries JavaScript -> IDL -> API specification, so you can just remove the statement and be done with it. 126489 3 watsonm 2016-05-23 22:47:25 +0000 I believe this has already been fixed. Step 14 or wrapKey refers to conversion *back* from an IDL object to an ECMAScript object which can then be stringified in the next step.