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

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

--- Comment #15 from Ryan Sleevi <sleevi@google.com> ---
(In reply to Boris Zbarsky from comment #14)
> > 1) Set an internal slot for the IDL/internal representation of an object, so
> > that it can be accessed and/or mutated without any externally-visible (to ES)
> > effects
> > 2) Set an ADDITIONAL internal slot for the "public" representation, which would
> > be the "cached" object
> 
> Yes.  I assumed that's what Mark was talking about.  Did I misunderstand?

My understanding was that the proposed solution was to set [[usages]] (e.g.
what affects internal consumption), rather than introduce a [[usages_exposed]]
that reflects the attribute value in a cached manner, but is not used for any
access checks.

I don't understand why we'd Object.freeze if doing a [[usages_exposed]] - don't
the existing [Cached] IDL objects already reflect any ES modifications to them
(directly or via prototype chain)? That is, they always return the same ES
object - which may have been mutated.

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

Received on Wednesday, 8 October 2014 22:06:07 UTC