- From: Joshua Bell <notifications@github.com>
- Date: Mon, 17 Jul 2017 23:21:30 +0000 (UTC)
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 17 July 2017 23:22:36 UTC
Thanks! Closing this out. @brettz9 - good enumeration of some of the implementation risks and mitigations. For now I'm leaving those out, as they're ostensibly covered by the existing non-normative note "If an implementation uses a storage mechanism which does not support arbitrary strings, the implementation can use an escaping mechanism or something similar to map the provided name to a string that it can store." although maybe it could use the word "safely" in there somewhere. -- 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/207#issuecomment-315912965
Received on Monday, 17 July 2017 23:22:36 UTC