[google-appengine] Re: Channel API broken in Chrome Extensions

2011-04-14 Thread RSW
Moishe, Glad to hear it and thanks for the quick follow-up. I'll send you an email shortly for the static file. I wonder, is it generally possible/wise to use a static file in order to ensure predictable reliability? I.e. as with jquery served from the Google Libraries API, I can get the versi

[google-appengine] Re: Channel API broken in Chrome Extensions

2011-04-14 Thread Moishe
Okay, I've identified and fixed the problem, and am working on getting a fix rolled out to production. No ETA on that yet. In the meantime if you'd like a patched jsapi file that you can serve statically from your own site, contact me directly at moishel at google.com. -- You received this messa

[google-appengine] Re: Channel API broken in Chrome Extensions

2011-04-14 Thread elias_naur
I have the same problem here, trying to use an App Engine Channel from a Chrome extension fails to trigger onmessage/onopen/onerror. Nothing happens, and there's nothing in the extension background page console log. It worked fine a few days ago, and I haven't changed any extension code in that tim

[google-appengine] Re: Channel API broken in Chrome Extensions

2011-04-14 Thread RSW
Hi Moishe, I am using the stable release, and the current up-to-date version is 10.0.648.204 (on a Mac). I only use the Channel API within a chrome extension, so I can't say if there's a problem in other cases. -Ronald. -- You received this message because you are subscribed to the Google

[google-appengine] Re: Channel API broken in Chrome Extensions

2011-04-14 Thread Moishe
Hi, Ronald. I'm looking into this today, will try to get back to you later on with some more information. Is this only happening with Chrome extensions? Which channel of Chrome are you running - dev, beta or main? Thanks! -Moishe -- You received this message because you are subscribed to the G