On Sep 8, 5:16 pm, Michael Weber <[email protected]> wrote: > Might be a port problem -- I noticed that example passes the optional > connectInfo param (the object with the "name" key) in the call to > connect. > > I was struggling to get port communications working today, and I found > that my ports do not work in either direction (to extension or to > content scripts) if I pass the optional connectInfo param in the > connect call. If I leave it out, then it works. > > This was with my build from source as of late afternoon Aug 25, 2009. > Rebuilding today's tree to check if it works now.
Just tested with a new build, and tested a bit more carefully. Seems that passing a connectInfo object to chrome.extension.connect causes problems -- messages do not arrive in the my toolstrip's handler. Passing connectInfo info chrome.tabs.connect is OK -- messages arrive in my content script's handler. However, the name is not passed in. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
