967879 - DOMHelpers.onceDOMReady should return a promise

Status: RESOLVED WONTFIX

(DevTools :: Framework, defect)

Description

[Joe Walker [:jwalker]]

Attachment: domhelper.patch

Die, callbacks. Die.
Maybe we don't care about DOMHelpers much, but this could result in quite a bit of code simplification.
It's a bit of a drive-by patch and uses the wrong promise lib right now.

Comment 1

[Brandon Benvie [:benvie]]

Comment on attachment 8370383 [details] [diff] [review]
domhelper.patch

Review of attachment 8370383 [details] [diff] [review]:
-----------------------------------------------------------------

This looks like a welcome cleanup; promises compose much more cleanly with other promises. I think you *may* have to keep using the addon-sdk's promise implementation with where this is currently being used, until bug 943510 lands. You should definitely try using Promise.jsm first and see if it works. If not then feel free to fall back to using addon-sdk's promise.

::: browser/devtools/shared/DOMHelpers.jsm
@@ +157,2 @@
>          // We want to avoid that so we execute the callback in the next queue.
>          Services.tm.mainThread.dispatch(callback, 0);

This should be conditional since callback will be optional now.

@@ +157,4 @@
>          // We want to avoid that so we execute the callback in the next queue.
>          Services.tm.mainThread.dispatch(callback, 0);
> +
> +        promise.resolve(undefined);

deferred.resolve