summaryrefslogtreecommitdiffstats
path: root/chrome/browser/extensions/extension_message_service.h
Commit message (Expand)AuthorAgeFilesLines
* Don't send the channel-disconnect message if the recipient is in the processmpcomplete@chromium.org2009-09-091-1/+2
* Extension ports devtools remote service.sdoyon@chromium.org2009-08-261-12/+26
* Exposes a chrome.devtools object to extensions. This allows extensions to ca...mpcomplete@chromium.org2009-08-241-0/+3
* Committing for Siggi based on review:mad@google.com2009-08-081-4/+5
* Coverity: Pass strings by reference.jhawkins@chromium.org2009-07-241-4/+5
* Split the IPC code into ipc/agl@chromium.org2009-07-221-1/+1
* Changed the extension.connect() API not to broadcast to all tabs. Added ampcomplete@chromium.org2009-07-201-46/+57
* Add an optional channel name to the extension message connect event.mpcomplete@chromium.org2009-07-131-12/+28
* Make the API to open a message channel symmetric, so it works the same whethe...mpcomplete@chromium.org2009-07-091-43/+23
* Fix some issues with extension messaging:mpcomplete@chromium.org2009-07-021-3/+5
* Send port disconnect events when a frame is unloaded.mpcomplete@chromium.org2009-07-011-17/+20
* Revert 18765 to try to repair perf regressionjar@chromium.org2009-06-191-20/+17
* Send port-closed notification when a frame with ports unloads.mpcomplete@google.com2009-06-181-17/+20
* Add a port disconnect event for when one side of an extension message portmpcomplete@google.com2009-06-171-0/+6
* Reduce header dependencies in chrome/browser/phajdan.jr@chromium.org2009-06-161-1/+1
* Use a NotificationRegistrar to listen for notifications.pkasting@chromium.org2009-05-211-1/+3
* Allow connecting and messaging with extension ports by funneling externalmpcomplete@google.com2009-05-191-6/+32
* Remove executable bit from a bunch of files that shouldn't have it.evan@chromium.org2009-05-111-0/+0
* Add inspect links for all active views in chrome://extensions.aa@chromium.org2009-05-071-0/+8
* Pass down the opener tab when a message channel is opened to an extension.mpcomplete@google.com2009-05-011-37/+36
* Only send events to renderers that are listening to an event.Notify browser w...erikkay@google.com2009-05-011-0/+16
* Arrange so ExtensionMessageService::RendererReady is called on the IO thread.mpcomplete@google.com2009-04-231-12/+15
* Remove ExtensionProcessManager and move its functionality ontompcomplete@google.com2009-04-161-1/+4
* Initial plumbing for sending events from the browser to extension renderers. ...rafaelw@chromium.org2009-04-161-0/+2
* Prevent an extension from double observing a message filter.maruel@chromium.org2009-04-141-1/+5
* Fix a crash where the ResourceMessageFilter is deleted before apaulg@google.com2009-04-141-3/+6
* Introducing ExtensionProcessManager. This manages the ExtensionViews tompcomplete@google.com2009-04-091-1/+4
* Add code to support 2-way communication between extensions and renderers. Th...mpcomplete@google.com2009-04-021-25/+40
* Rename ExtensionMessageService::PostMessage because windows #defines that tompcomplete@google.com2009-03-231-1/+1
* Initial rev at a message passing API for extensions. So far, only passingmpcomplete@google.com2009-03-231-0/+73
generated by cgit v1.1 at 2025-01-21 04:10:08 +0000