Re: Seeing is believing?
On 11/4/2010 3:00 AM, Richard Maher wrote:
Hi Daniel,
"Daniel Pitts"<newsgroup.spamfilter@virtualinfinity.net> wrote in message
news:NZsAo.3996$8m.468@newsfe09.iad...
On 11/3/2010 7:03 AM, Richard Maher wrote:
8<
Do you not see the same thread being used from init() [up until the code
that calls JSObject.getWindow(this)] then isAuthorized receives control
of
the very same thread, and when that finishes the rest of init() gets
processed.
So, the problem appears to be that JSObject.getWindow(this) actually cedes
control back to the JS engine parser.
No, I/we can put up with this wierdness; what I cannot countenance is Chrome
*and specifically/uniquely Chrome* draining-the-queue via the same bloody
Thread that init() is running in!
Actually, I think you've put the cart before the horse. What Chrome
appears to be doing is drainging-the-queue in whatever thread happens to
call JSObject.getWindow(...). (You could verify this assumption by
printing "about to get window" and "finished getting window" around that
call).
This isn't necessarily expected or unexpected behavior. Armed with this
knowledge, you should be able to work around the chrome issue, and not
worry about it any more.
--
Daniel Pitts' Tech Blog: <http://virtualinfinity.net/wordpress/>