[w3c/IndexedDB] Implementation limits on keys (#344)

IndexedDB implementations may have limits on keys. These limits may come from the underlying storage system (perhaps the underlying database has a limit on index key sizes) or from a desire to preserve system stability and performance.

We should expose limits in existing implementations, to facilitate feature detection in this area. Sites can use alternate code paths or disable features based on the limits.

To kick things off, here are two limits from Chrome that I would like to expose, together with proposed API.

`IDBKeyRange.maxArrayLength` - Maximum length of an array used in an IndexedDB key. This is currently 1,000,000 in Chrome.
`IDBKeyRange.maxDepth` - Maximum recursive depth of arrays/objects in an IndexedDB key. This is currently 2,000 in Chrome.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/IndexedDB/issues/344