According to http://dev.w3.org/2009/dap/file-system/pub/FileSystem/#methods , the third parameter to requestFileSystem (successCallback) is not optional and can not be null. This test attempts to call the method without this parameter and checks for the required TypeError. Expected behavior: TypeError: not enough arguments Actual behavior: no exception thrown
Created attachment 110164 [details] Patch
Comment on attachment 110164 [details] Patch Attachment 110164 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/10015095 New failing tests: fast/filesystem/simple-required-arguments.html
Whoops, obviously these shouldn't have the review flag set since they are known failing tests.
(In reply to comment #3) > Whoops, obviously these shouldn't have the review flag set since they are known failing tests. It’s OK to land an expected failing result. The patch that fixes the bug just patches the expectation file to expect success instead of failure. We could group more of these tests in a single file, too, by the way. I think the tests are pretty clear even if there are a lot of them all in one test file.
Created attachment 117678 [details] Patch
Comment on attachment 117678 [details] Patch Attachment 117678 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/10729255 New failing tests: fast/filesystem/filesystem-no-callback-null-ptr-crash.html
Created attachment 118271 [details] Patch
Comment on attachment 118271 [details] Patch Clearing flags on attachment: 118271 Committed r102305: <http://trac.webkit.org/changeset/102305>
All reviewed patches have been landed. Closing bug.