- From: Boris Zbarsky <bzbarsky@MIT.EDU>
- Date: Wed, 09 Jul 2014 15:37:53 -0400
- To: Ryan Sleevi <sleevi@google.com>, Richard Barnes <rlb@ipv.sx>
- CC: "public-webcrypto@w3.org" <public-webcrypto@w3.org>
On 7/9/14, 3:34 PM, Ryan Sleevi wrote: > Regarding how to treat null, yes, we should treat it the same way > AES-GCM handles an empty additionalData I would actually recommend dropping nullability here altogether, unless there's some sort of back compat need. Missing should be treated as empty, ArrayBuffer and ArrayBufferView should be copied as already in the spec, null should just throw. -Boris
Received on Wednesday, 9 July 2014 19:38:23 UTC