Fix URI policies without fetch causing lost-signal.

Fixes <https://code.google.com/p/google-caja/issues/detail?id=1579>.

Domado's uriFetch now always invokes its callback, one way or another;
particularly if the URI policy object contains no 'fetch' method.

@r5609

[felix8a, 2013-10-02 03:43:04]

https://codereview.appspot.com/14228045/diff/1/src/com/google/caja/plugin/dom...
File src/com/google/caja/plugin/domado.js (right):

https://codereview.appspot.com/14228045/diff/1/src/com/google/caja/plugin/dom...
src/com/google/caja/plugin/domado.js:92: window.setTimeout(function() {
callback({}); }, 0);
this will invoke callback even if there isn't one? is that intentional?

[kpreid2, 2013-10-02 20:36:14]

Fixes <https://code.google.com/p/google-caja/issues/detail?id=1579>.

Domado's uriFetch now always invokes its callback, one way or another;
particularly if the URI policy object contains no 'fetch' method.

[kpreid2, 2013-10-02 20:36:45]

https://codereview.appspot.com/14228045/diff/1/src/com/google/caja/plugin/dom...
File src/com/google/caja/plugin/domado.js (right):

https://codereview.appspot.com/14228045/diff/1/src/com/google/caja/plugin/dom...
src/com/google/caja/plugin/domado.js:92: window.setTimeout(function() {
callback({}); }, 0);
On 2013/10/02 03:43:04, felix8a wrote:
> this will invoke callback even if there isn't one? is that intentional?

Now checked: there is never not a callback, and besides, uriFetch can't do
anything useful if there isn't one. So, I have removed "|| !callback".

[felix8a, 2013-10-02 22:51:44]

lgtm