IndexedDB: WebKit API changes to support upgradeneeded methods and events
Created attachment 154239 [details] Patch
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
Josh, could you take a look at this?
Comment on attachment 154239 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=154239&action=review LGTM, just naming nits. > Source/WebKit/chromium/public/WebIDBCallbacks.h:61 > + virtual void onBlocked(long long existingVersion) { WEBKIT_ASSERT_NOT_REACHED(); } Is there significance to calling this "existingVersion" rather than "oldVersion"? > Source/WebKit/chromium/public/WebIDBDatabaseCallbacks.h:38 > + virtual void onVersionChange(long long currentVersion, long long requestedVersion) { WEBKIT_ASSERT_NOT_REACHED(); } Can these be "oldVersion" and "newVersion" to align with the spec properties?
Comment on attachment 154239 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=154239&action=review >> Source/WebKit/chromium/public/WebIDBCallbacks.h:61 >> + virtual void onBlocked(long long existingVersion) { WEBKIT_ASSERT_NOT_REACHED(); } > > Is there significance to calling this "existingVersion" rather than "oldVersion"? No, thanks for catching that. >> Source/WebKit/chromium/public/WebIDBDatabaseCallbacks.h:38 >> + virtual void onVersionChange(long long currentVersion, long long requestedVersion) { WEBKIT_ASSERT_NOT_REACHED(); } > > Can these be "oldVersion" and "newVersion" to align with the spec properties? SG.
Created attachment 154278 [details] Patch
WebKit API reviewers, this is ready for you.
Comment on attachment 154278 [details] Patch Clearing flags on attachment: 154278 Committed r123710: <http://trac.webkit.org/changeset/123710>
All reviewed patches have been landed. Closing bug.