[Webkit-unassigned] [Bug 60197] New: IndexedDB result of deleting a record should be true or false

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=60197

           Summary: IndexedDB result of deleting a record should be true
                    or false
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: Unspecified
        OS/Version: Unspecified
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: New Bugs
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: pilgrim at chromium.org
                CC: fishd at chromium.org, tony at chromium.org,
                    hans at chromium.org, dgrogan at chromium.org,
                    pilgrim at chromium.org


Original test: http://mxr.mozilla.org/mozilla2.0/source/dom/indexedDB/test/test_odd_result_order.html?force=1

This test is adapted from a test in Mozilla's IndexedDB test suite. It checks that the result property of a request after an asychronous delete operation is either true (if the record existed and was deleted successfully) or false (if the record did not exist).

WebKit fails this test. The result property is always null, regardless of whether the delete operation succeeded or failed.

Citation: http://dvcs.w3.org/hg/IndexedDB/raw-file/tip/Overview.html#dfn-steps-for-deleting-a-record-from-an-object-store "If no record exists with key key in store, then the result of this algorithm is false... [steps for successful deletion, and then] The result of this algorithm is true."

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.