- From: Boris Zbarsky <bzbarsky@mit.edu>
- Date: Tue, 17 May 2016 14:38:04 -0400
- To: public-webcrypto@w3.org
On 5/17/16 2:20 PM, Jim Schaad wrote: > Current testing runs have the following results: > > Chrome Canary has 15 fail cases. These are: > class string of Crypto.prototype expected "[object CryptoPrototype]" but got "[object Crypto]" > class string of CryptoKey.prototype expected "[object CryptoKeyPrototype]" but got "[object CryptoKey]" > class string of SubtleCrypto.prototype expected "[object SubtleCryptoPrototype]" but got "[object SubtleCrypto]" That's because of https://www.w3.org/Bugs/Public/show_bug.cgi?id=28244#c6 I would think. That doesn't explain the exceptions, though. > Mozilla stable passes all tests cleanly when dealing with the window interface and fails all tests for the worker side with the error > assert_own_property: self does not have own property "Crypto" expected property "Crypto" missing Web crypto is not available in workers until Firefox 48, which is currently the dev edition channel. -Boris
Received on Tuesday, 17 May 2016 18:38:33 UTC