Google App Engine Channel API and Chrome Extensions -


over christmas implemented code open channel app engine application using channel api , working fine.

i returned code , find broken, , problem seems lie in talkgadget client code trying load frame.

i took snapshot of code returned /_ah/channel/jsapi on december 21 , comparing today's code.

when older version tried talkgadget.google.com/talkgadget/d?token=[my-token] hardcoded use http. sensibly enough, code later changed check page's protocol in document.location , adapt cases https used. problem when running in chrome extension grabs chrome-extension: protocol , naturally channel fails open in extension.

setting base of background page appspot url not change document.location, although had vague notion should. (not sure standards say.)

is there workaround this? 1 thought create own iframe loaded site, nest actual channel iframe, complicating things.

i wonder if moishe or else on app engine team comment on this. seems bug , code should take chrome extensions either testing protocol , searching base tag alternative, or provide way configure through javascript object.

yep, bug. there's fix submitted, , it's in process of rolling out production; it'll out in week.

in meantime, idea of iframe embedded in extension should work.


Comments

Popular posts from this blog

python - Scipy curvefit RuntimeError:Optimal parameters not found: Number of calls to function has reached maxfev = 1000 -

c# - How to add a new treeview at the selected node? -

java - netbeans "Please wait - classpath scanning in progress..." -