<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - CryptoKeyPair objects are not structured cloneable, therefore they cannot be put in IndexedDB"
href="https://bugs.webkit.org/show_bug.cgi?id=164868#c9">Comment # 9</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - CryptoKeyPair objects are not structured cloneable, therefore they cannot be put in IndexedDB"
href="https://bugs.webkit.org/show_bug.cgi?id=164868">bug 164868</a>
from <span class="vcard"><a class="email" href="mailto:beidson@apple.com" title="Brady Eidson <beidson@apple.com>"> <span class="fn">Brady Eidson</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=164868#c8">comment #8</a>)
<span class="quote">> (In reply to <a href="show_bug.cgi?id=164868#c7">comment #7</a>)
> > I believe the reason Chrome and Firefox allow the put is that they do not
> > recognize the CryptoKeyPair as a "CryptoKeyPair" - They think it's an
> > "Object"
> >
> > And "Objects" are structured cloneable as long as each of their properties
> > are.
>
> Got it.
>
> At one point in the history of the spec, CryptoKeyPair objects were their
> own interface, therefore their own explicit object type.
>
> Now they're just an object dictionary
> (<a href="https://w3c.github.io/webcrypto/Overview.html#keypair">https://w3c.github.io/webcrypto/Overview.html#keypair</a>), which means they
> are an "Object", which means they are structured cloneable</span >
Fixing this is just a matter of fixing our IDL situation for CryptoKeyPair.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>