Bug 720697 comment #12:
> >+nsHTMLCanvasElement::MozFetchAsStream(nsIInputStreamCallback *aCallback,
> >+ return aCallback->OnInputStreamReady(asyncData);
> It's generally a bad idea to design an API to be async-friendly, but then
> invoke the callback synchronously - people can start depending on that,
> making your life difficult when it comes time to change it in the future.
> Can you use a runnable here?
Created attachment 594102 [details] [diff] [review]
Comment on attachment 594102 [details] [diff] [review]
Dispatching the callback on another thread is absolutely not what we want here.
Created attachment 594145 [details] [diff] [review]
Fresh patch, using the main thread.