On Nov 8, 7:31 pm, Aaron Boodman <a...@chromium.org> wrote:
> But stepping back, what are you actually trying to do? Why does foo()
> take so long to execute? One scenario I can imagine is that foo()
> contains a synchronous XHR and that the first setIcon() is setting the
> icon to "loading" and the second is setting it to "logged in". In that
> case, IMO, the best solution is to not use synchronous XHR. This will
> allow the first setIcon() call to go through immediately.
Yes, it's synchronous XHR. The problem with asynchronous XHR is that
it's complicated to get variables in and out of the onreadystatechange
function, and there are several XHR involved here with one using data
returned by the other.
I will try embedding and drawing a base64 encoded image.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-extensions" group.
To post to this group, send email to chromium-extensions@googlegroups.com
To unsubscribe from this group, send email to
chromium-extensions+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/chromium-extensions?hl=en
-~----------~----~----~----~------~----~------~--~---
