Bug 35047 - Database.transaction() should accept nulls for optional parameters
Summary: Database.transaction() should accept nulls for optional parameters
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Dumitru Daniliuc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-17 11:50 PST by Dumitru Daniliuc
Modified: 2010-02-17 14:47 PST (History)
2 users (show)

See Also:


Attachments
patch (1.64 KB, patch)
2010-02-17 12:03 PST, Dumitru Daniliuc
dumi: commit-queue-
Details | Formatted Diff | Diff
patch (4.26 KB, patch)
2010-02-17 13:15 PST, Dumitru Daniliuc
dglazkov: review+
dumi: commit-queue-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Dumitru Daniliuc 2010-02-17 11:50:01 PST
Database.transaction() complains when 'null' is used for the transaction success or error callback. It should be treated as "no callback specified".
Comment 1 Dumitru Daniliuc 2010-02-17 12:03:51 PST
Created attachment 48921 [details]
patch

The JSC bindings know how to deal with null callbacks. Only Chromium's bindings needed to be fixed.
Comment 2 Dumitru Daniliuc 2010-02-17 13:15:35 PST
Created attachment 48929 [details]
patch
Comment 3 Dimitri Glazkov (Google) 2010-02-17 13:40:05 PST
Comment on attachment 48929 [details]
patch

ok.
Comment 4 Dumitru Daniliuc 2010-02-17 14:47:54 PST
Landed as r54910.