- From: <bugzilla@jessica.w3.org>
- Date: Mon, 15 Apr 2013 20:43:13 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20394
Joshua Bell <jsbell@chromium.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Joshua Bell <jsbell@chromium.org> ---
(In reply to comment #5)
> What's left is a smattering of uses of <code>Array</code> throughout the
> spec far away from the method input definitions. Most of those are around
> keys (which should now be correct) but some are around key paths; those
> should more abstractly refer to a sequences, lists, or sets, not the input
> type.
(In reply to comment #6)
> There are still issues here for keyPath. I filed bug 21555 on those.
Apart from the issues in 21555, I've updated the places that describe
array-type key paths to use sequence<DOMString> consistently in
https://dvcs.w3.org/hg/IndexedDB/rev/5d920000beba
The pedantic part of me would like to take this further and refer to them even
more abstractly as "sequences of strings" but this is probably sufficient.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 15 April 2013 20:43:15 UTC