- From: Philip Jägenstedt <notifications@github.com>
- Date: Wed, 27 Apr 2016 07:58:01 -0700
- To: w3c/IndexedDB <IndexedDB@noreply.github.com>
- Cc:
Received on Wednesday, 27 April 2016 14:59:11 UTC
item on Location does not look promising. If DOMStringList cannot be purged entirely from the platform, is it worthwhile trying to get rid of it from IndexedDB alone? Given what location.ancestorOrigins is for, it is plausible that almost all of the usage comes from a single origin, so if one could fine out what it is it might be possible to drive down the usage of that enough to eliminate DOMStringList. --- 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/28#issuecomment-215110692
Received on Wednesday, 27 April 2016 14:59:11 UTC