Calling db.createObjectStore(null) should behave identically to calling db.createObjectStore("null"). I have double-checked this (highly unintuitive) behavior with the author of the WebIDL spec and he confirms it ( http://krijnhoetmer.nl/irc-logs/whatwg/20110622#l-187 ). There was also apparently a WebIDL spec bug recently asking to change this behavior, but it was WONTFIXED ( http://www.w3.org/Bugs/Public/show_bug.cgi?id=12798 ). End result: null values for DOMString arguments get stringified to the four-character string "null". This affects several functions in WebKit's IndexedDB implementation. I am filing separate bugs for each of them. (See bug 63110 and bug 63114, for instance.) Patch attached.
Created attachment 98113 [details] Patch
Comment on attachment 98113 [details] Patch Attachment 98113 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/8920225
Created attachment 98122 [details] Archive of layout-test-results from ec2-cr-linux-02 The attached test failures were seen while running run-webkit-tests on the chromium-ews. Bot: ec2-cr-linux-02 Port: Chromium Platform: Linux-2.6.35-28-virtual-x86_64-with-Ubuntu-10.10-maverick
Consolidating several bugs. *** This bug has been marked as a duplicate of bug 63140 ***
Comment on attachment 98113 [details] Patch Marking obsolete as the bug closed.