This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25386 - Arrays and iterables
Summary: Arrays and iterables
Status: RESOLVED FIXED
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-18 07:53 UTC by Anne
Modified: 2014-06-17 06:11 UTC (History)
3 users (show)

See Also:

Attachments

Description Anne 2014-04-18 07:53:36 UTC 
Several methods take "KeyUsage[] keyUsages" as argument. That should really be sequence there: "sequence<KeyUsage> keyUsages"

It should accept any JavaScript iterable, not just IDL-arrays (which are going away).


The usage in https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html#dfn-Key you want to turn into either returning a readonly frozen array or a method that returns a snapshot, not sure if the TAG reached any conclusions yet.
Comment 2 Anne 2014-06-17 05:36:30 UTC 
Where was the prose added for usages?
Comment 3 Ryan Sleevi 2014-06-17 05:48:49 UTC 
Anne,

What prose, in particular, were you expecting?

The input argument, being sequence<>, should address the WebIDL conversion issues raised with [].

The exposure of this, as an attribute, has now been handled as part of the overall treatment/conversion of KeyAlgorithm to a dictionary (ergo ES object), rather than as an IDL interface.

If there are concerns still unaddressed, let me know, as I believe the issue raised was addressed.
Comment 4 Anne 2014-06-17 06:11:45 UTC 
Looks good, thanks. I missed the [[usages]] refactoring in the above commit and assumed it wasn't made.