W3C home > Mailing lists > Public > public-webcrypto@w3.org > May 2016

RE: Pull request for IDL testing

From: Jim Schaad <ietf@augustcellars.com>
Date: Tue, 17 May 2016 12:40:46 -0700
To: "'Boris Zbarsky'" <bzbarsky@mit.edu>, <public-webcrypto@w3.org>
Message-ID: <02d801d1b074$025cdbf0$071693d0$@augustcellars.com>


> -----Original Message-----
> From: Boris Zbarsky [mailto:bzbarsky@mit.edu]
> Sent: Tuesday, May 17, 2016 11:38 AM
> To: public-webcrypto@w3.org
> Subject: Re: Pull request for IDL testing
> 
> 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.

In that case it falls under the rubric of "expected behavior" and I will not worry about it any more

> 
> That doesn't explain the exceptions, though.

I expect that Eric might have some ideas.

> 
> > 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.

I expected that was the case, but I still need to get to the point where I can have both the dev and stable versions of Firefox open at the same time.  I have found the instructions; I just haven't done them.

Jim

> 
> -Boris
Received on Tuesday, 17 May 2016 19:41:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 17 May 2016 19:41:11 UTC