Updates:
Status: Fixed
Owner: fin...@chromium.org
Comment #8 on issue 13936 by fin...@chromium.org: Implement extension
specific events
http://code.google.com/p/chromium/issues/detail?id=13936
(No comment was entered for this change.)
--
You received this message because you a
Comment #7 on issue 13936 by bugdro...@chromium.org: Implement extension
specific events
http://code.google.com/p/chromium/issues/detail?id=13936
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=20714
-
Comment #6 on issue 13936 by mpcompl...@chromium.org: Implement extension
specific events
http://code.google.com/p/chromium/issues/detail?id=13936
"I thought the state in EMS was a bit different since it is really keeping
track of
ports. Do you think the state should be shared somehow?"
I d
Comment #5 on issue 13936 by a...@chromium.org: Implement extension specific
events
http://code.google.com/p/chromium/issues/detail?id=13936
I thought the state in EMS was a bit different since it is really keeping
track of
ports. Do you think the state should be shared somehow?
""When Exte
Comment #4 on issue 13936 by mpcompl...@chromium.org: Implement extension
specific events
http://code.google.com/p/chromium/issues/detail?id=13936
"Keep a map in ExtensionProcessManager maintaining which extensions are
running in
which processes."
FYI, ExtensionMessageService already has su
Updates:
Cc: mpcompl...@chromium.org erik...@chromium.org
Comment #2 on issue 13936 by a...@chromium.org: Implement extension specific
events
http://code.google.com/p/chromium/issues/detail?id=13936
+mpcomplete, erikkay
Ok, to recap, the desire is to have an API like this:
chrome.pag
Comment #1 on issue 13936 by bugdro...@chromium.org: Implement extension
specific events
http://code.google.com/p/chromium/issues/detail?id=13936
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=19717
-
