summaryrefslogtreecommitdiffstats
path: root/chrome/renderer/resources/renderer_extension_bindings.js
Commit message (Expand)AuthorAgeFilesLines
* Adding support for i18n to content scripts.cira@chromium.org2009-12-291-3/+10
* Add stub functions for chrome.* APIs in content scripts. asargent@chromium.org2009-11-131-1/+49
* Change the extension.onRequest even to include the sender info.mpcomplete@chromium.org2009-10-291-5/+6
* Implement extension.sendRequest, a simpler way to do messaging.mpcomplete@chromium.org2009-10-231-4/+54
* Implement chrome.extension.connectExternal and fix various API inconsistencies.mpcomplete@chromium.org2009-10-091-37/+54
* Extension API Renaming/Consistency changesrafaelw@chromium.org2009-08-281-4/+8
* Fix port disconnect so that it's refcounted. This fixes a bug where a channelmpcomplete@chromium.org2009-07-271-1/+4
* Add an optional channel name to the extension message connect event.mpcomplete@chromium.org2009-07-131-8/+17
* Make the API to open a message channel symmetric, so it works the same whethe...mpcomplete@chromium.org2009-07-091-12/+20
* Fix some issues with extension messaging:mpcomplete@chromium.org2009-07-021-8/+16
* Send port disconnect events when a frame is unloaded.mpcomplete@chromium.org2009-07-011-1/+2
* Refactor extension bindings to share code, avoid exposing hidden variablesmpcomplete@chromium.org2009-06-301-11/+26
* Revert 18765 to try to repair perf regressionjar@chromium.org2009-06-191-13/+0
* Send port-closed notification when a frame with ports unloads.mpcomplete@google.com2009-06-181-0/+13
* Add a port disconnect event for when one side of an extension message portmpcomplete@google.com2009-06-171-5/+12
* BUG=12192rafaelw@chromium.org2009-05-301-3/+6
* BUG=11200rafaelw@chromium.org2009-05-051-16/+16
* Pass down the opener tab when a message channel is opened to an extension.mpcomplete@google.com2009-05-011-1/+5
* Adding a comment stating what needs to be recompiled in orderfor changes to t...finnur@chromium.org2009-04-171-0/+9
* Initial plumbing for sending events from the browser to extension renderers. ...rafaelw@chromium.org2009-04-161-1/+1
* Miscellaneous API sprucing.aa@chromium.org2009-04-161-5/+3
* TBR: Revert "Miscellaneous API sprucing."aa@chromium.org2009-04-151-3/+5
* Miscellaneous API sprucing.aa@chromium.org2009-04-151-5/+3
* Hook up extension events to the json parser, and change the extension messagempcomplete@google.com2009-04-131-1/+4
* Add aa's Event class to our javascript bindings and use it in our extensionmpcomplete@google.com2009-04-081-71/+42
* Add code to support 2-way communication between extensions and renderers. Th...mpcomplete@google.com2009-04-021-0/+93
generated by cgit v1.1 at 2025-01-10 08:34:24 +0000