[Bug 26322] Definitions "algorithm" and "usages" properties of CryptoKey make no sense

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26322

--- Comment #12 from Boris Zbarsky <bzbarsky@mit.edu> ---
> For [[usages]] we will explicitly state the values of the members of the Array.

Or create it from an IDL sequence.  That would make sure that the array is
created in the right way (the one that's side-effect-free).  Just stating the
values of the Array members doesn't define how those members get defined on the
Array, which is important here.

> The algorithm and usages attributes, rather than 'reflecting' the contents of
> the ... internal slot will simply 'return' the contents of that slot.

Yep.

And changing usages (if that's possible) will throw the array in [[usages]]
away and create a new one?

> Does this work ?

I think so, yes.

> Is there a reference we should use for the process of
> 'freezing' an object ?

I would say something like "Call the initial value of Object.freeze on X" for
freezing X, possibly with a link to
http://people.mozilla.org/~jorendorff/es6-draft.html#sec-object.freeze

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 8 October 2014 16:15:35 UTC