RESOLVED FIXED 108638
[Chromium] Move IDBFactoryBackendInterface to WebCore
https://bugs.webkit.org/show_bug.cgi?id=108638
Summary [Chromium] Move IDBFactoryBackendInterface to WebCore
Mark Pilgrim (Google)
Reported 2013-02-01 07:52:33 PST
[Chromium] Move IDBFactoryBackendInterface to WebCore
Attachments
Patch (14.09 KB, patch)
2013-02-01 07:54 PST, Mark Pilgrim (Google)
no flags
Patch (12.96 KB, patch)
2013-02-01 15:19 PST, Mark Pilgrim (Google)
no flags
Patch (13.00 KB, patch)
2013-02-04 07:24 PST, Mark Pilgrim (Google)
no flags
Mark Pilgrim (Google)
Comment 1 2013-02-01 07:54:08 PST
Mark Pilgrim (Google)
Comment 2 2013-02-01 07:55:20 PST
Comment on attachment 186048 [details] Patch Same technique as bug 108488.
Adam Barth
Comment 3 2013-02-01 11:10:37 PST
Comment on attachment 186048 [details] Patch Ok.
Adam Barth
Comment 4 2013-02-01 11:13:56 PST
Comment on attachment 186048 [details] Patch I'm not super excited about this patch. The difference between this patch and the media player patch is that IndexedDB should be scoped to some sort of storage context. For example, the PageGroup, rather than being a static. That said, I think we should go forward with this patch for two reasons: 1) We're already using a static, so we're not really losing anything. 2) We don't currently have the notion of a "storage context", so there isn't really anything to hang this off of today. I suspect we'll eventually revisit this issue, but at least the problem is more visible now that there is code in the initialize function that mentions the static.
Mark Pilgrim (Google)
Comment 5 2013-02-01 15:19:52 PST
Mark Pilgrim (Google)
Comment 6 2013-02-01 15:20:43 PST
Comment on attachment 186159 [details] Patch Resubmitting same patch due to SVN weirdness. Let's make sure EWS goes green before committing.
Mark Pilgrim (Google)
Comment 7 2013-02-01 15:23:09 PST
(In reply to comment #4) > (From update of attachment 186048 [details]) > I'm not super excited about this patch. The difference between this patch and the media player patch is that IndexedDB should be scoped to some sort of storage context. For example, the PageGroup, rather than being a static. Can't use PageGroup because workers. (We tried.) > I suspect we'll eventually revisit this issue, but at least the problem is more visible now that there is code in the initialize function that mentions the static. Agreed.
WebKit Review Bot
Comment 8 2013-02-01 16:03:24 PST
Comment on attachment 186159 [details] Patch Attachment 186159 [details] did not pass cr-linux-debug-ews (chromium-xvfb): Output: http://queues.webkit.org/results/16341195
Adam Barth
Comment 9 2013-02-02 00:05:30 PST
Comment on attachment 186159 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=186159&action=review > Source/WebCore/Modules/indexeddb/chromium/IDBFactoryBackendInterfaceChromium.cpp:44 > + ASSERT(s_idbFactoryCreateFunction); Looks like you've got the wrong name in this ASSERT.
Mark Pilgrim (Google)
Comment 10 2013-02-04 07:24:48 PST
Mark Pilgrim (Google)
Comment 11 2013-02-04 07:25:27 PST
Comment on attachment 186372 [details] Patch FIxed ASSERT.
WebKit Review Bot
Comment 12 2013-02-04 10:53:38 PST
Comment on attachment 186372 [details] Patch Clearing flags on attachment: 186372 Committed r141784: <http://trac.webkit.org/changeset/141784>
WebKit Review Bot
Comment 13 2013-02-04 10:53:43 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.