135029 2014-07-17 15:40:19 -0700 WK2 should have API to support fetching and deleting IndexedDatabases on a per-origin basis 2014-07-28 13:01:19 -0700 1 1 1 Unclassified WebKit WebKit2 528+ (Nightly build) All All NEW InRadar P2 Normal --- 135035 135346 1 beidson webkit-unassigned andersca mhock sam thorton oldest_to_newest 1023125 0 beidson 2014-07-17 15:40:19 -0700 WK2 should have API to support fetching and deleting IndexedDatabases on a per-origin basis This is the same patter we have for KeyValueStorageManager, CookieManager, DatabaseManager, etc etc etc. Except we hope to not repeat the same mistake again and instead make a single API that can be used for all website data types, present and future. Work was already done on this last fall, adding the WKOriginDataManager API. That API doesn't actually do anything, so it isn't used anywhere, so we're still free to change it around. I plan to make it actually work for IndexedDatabases, and other data types can be migrated over 1-by-1 In radar - <rdar://problem/15917314> 1023128 1 beidson 2014-07-17 15:43:44 -0700 Call this an umbrella bug. First subtask filed as: https://bugs.webkit.org/show_bug.cgi?id=135030 Simplify WebOriginDataManager(Proxy) and rename to UIProcessOriginDataManager and ChildProcessOriginDataManager 1023156 2 beidson 2014-07-17 18:05:59 -0700 First real subtask: Clean up WKOriginDataManager and get it messaging to the DatabaseProcess - https://bugs.webkit.org/show_bug.cgi?id=135035 1025194 3 beidson 2014-07-28 13:01:19 -0700 Filed subtask https://bugs.webkit.org/show_bug.cgi?id=135346 to make the API actually operate on IDB