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

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

--- Comment #30 from Boris Zbarsky <bzbarsky@mit.edu> ---
> can you provide any example of any other Web Platform API that uses Freeze

Can you provide any example of any other Web Platform API that has an attribute
that returns JS arrays?  Fundamentally we're on new ground here.

> the huge number of interfaces with "readonly attributes" that fundamentally
> aren't readonly

More precisely that don't return immutable objects.  I did explain in my
comment why this case is fundamentally different, no?

We'll continue to ship this with frozen arrays until we figure out a way to
make them mutable that doesn't introduce security bugs from our point of view,
I guess.  We have some ideas for how to maybe make it work, but no ETA on when
we might be able to do it, so given the choice between not shipping webcrypto
at all and shipping with frozen arrays here, frozen arrays it is.

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

Received on Saturday, 8 November 2014 03:02:38 UTC