On Tue, Jul 28, 2009 at 6:02 PM, Matt Perry mpcompl...@chromium.org wrote:
Two suggestions (one I accidentally sent only to James):
chrome.extension.Port:
// ID of the extension at the other side of this port.
String senderID;
Port currently has a 'tab' property if the sender was a tab.
On Thu, Jul 30, 2009 at 10:44 AM, James Robinson jam...@google.com wrote:
On Tue, Jul 28, 2009 at 6:02 PM, Matt Perry mpcompl...@chromium.orgwrote:
Two suggestions (one I accidentally sent only to James):
chrome.extension.Port:
// ID of the extension at the other side of this port.
String
[bcc chromium-dev]
On Thu, Jul 30, 2009 at 2:01 PM, Matt Perry mpcompl...@chromium.org wrote:
On Thu, Jul 30, 2009 at 10:44 AM, James Robinson jam...@google.comwrote:
On Tue, Jul 28, 2009 at 6:02 PM, Matt Perry mpcompl...@chromium.orgwrote:
Two suggestions (one I accidentally sent only to
+chromium-dev
I think this is great. I suggest creating a wiki page with a design
for this so that we can refer to it whenever we implement, and a bug
that refers to the wiki page.
Up until now, we've been putting our designs here:
http://dev.chromium.org/developers/design-documents/extensions
On Tue, Jul 28, 2009 at 11:30 AM, Drew Wilsonatwil...@chromium.org wrote:
SGTM. Note that we're essentially duplicating (assumedly intentionally so)
the window.postMessage() APIs which require specifying a target domain and
whose connect event has a source and origin attribute specifying the
Thanks for the feedback. I've created
http://code.google.com/p/chromium/wiki/InterExtensionCommunication with the
proposal and would appreciate if someone with an @chromium account could
link to it from
http://dev.chromium.org/developers/design-documents/extensions. I copied
the proposal pretty
On Tue, Jul 28, 2009 at 12:09 PM, James Robinsonjam...@google.com wrote:
Thanks for the feedback. I've
created http://code.google.com/p/chromium/wiki/InterExtensionCommunication with
the proposal and would appreciate if someone with an @chromium account could
link to it
Done. I also created
On Tue, Jul 28, 2009 at 12:20 PM, Aaron Boodmana...@chromium.org wrote:
We'll always know what extension the onConnectExternal event will be fired
at when the connectExternal() call is made, so at the very least we could
promise that no onConnectExternal event will be fired at an extension
Two suggestions (one I accidentally sent only to James):
chrome.extension.Port:
// ID of the extension at the other side of this port.
String senderID;
Port currently has a 'tab' property if the sender was a tab. Maybe we
should group these:
chrome.extension.Port:
Object sender:
Object
