Always use safeCallbackApply to invoke fileSystem API callbacks.
commitba3dc42535b4a53c33236753812e3011dcb0202f
authorsammc@chromium.org <sammc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 4 Feb 2014 01:45:28 +0000 (4 01:45 +0000)
committersammc@chromium.org <sammc@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>
Tue, 4 Feb 2014 01:45:28 +0000 (4 01:45 +0000)
treebe07dd49d223adad6dc05c5e6faafb0653b7f2be
parent8a6cc28c36406b44206f1373d7aa87db57e1bb58
Always use safeCallbackApply to invoke fileSystem API callbacks.

Previously, for API methods where an Entry was provided to the callback,
if the callback throws an exception, it would be printed to the
background page's console. With this change, these exceptions are
reported the same way as those thrown by callbacks to other API methods,
including reporting the call stack to the original call.

BUG=314124

Review URL: https://codereview.chromium.org/146823005

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248654 0039d316-1c4b-4281-b951-d872f2087c98
chrome/renderer/resources/extensions/file_system_custom_bindings.js
chrome/renderer/resources/extensions/send_request.js