summaryrefslogtreecommitdiffstats
path: root/chrome/renderer/extensions/event_bindings.cc
Commit message (Expand)AuthorAgeFilesLines
* Attempt to fix a crash in extension bindings' CallFunctionInContext.mpcomplete@chromium.org2010-02-261-5/+17
* Track the parent_frame for content script contexts instead of the parent_cont...mpcomplete@chromium.org2010-02-091-17/+11
* Upstreaming WebKit.gypyaar@chromium.org2009-11-121-3/+3
* Eliminate WebView::GetDelegate and replace RenderViewSet with a map fromdarin@chromium.org2009-10-091-3/+3
* Use the current frame's URL when initializing the extension framework for a f...mpcomplete@chromium.org2009-09-291-5/+4
* Fix bug where content scripts can get GC'd if they don'taa@chromium.org2009-09-141-6/+16
* Try again to commit r24174: Change the way json_schema.js is loaded.aa@chromium.org2009-08-251-1/+1
* Revert r24217.aa@chromium.org2009-08-251-1/+1
* Change the way json_schema.js is loaded. This is required soaa@chromium.org2009-08-251-1/+1
* Validation of extension api callbacks and event parameters in DEBUGrafaelw@chromium.org2009-08-221-1/+12
* Allow extensions to use APIs that they didn't ask permission to use.mpcomplete@chromium.org2009-08-121-1/+6
* Switch to WebFrame from the WebKit API.darin@chromium.org2009-08-101-8/+9
* Add module-level permissions to extensions.mpcomplete@chromium.org2009-08-071-1/+11
* Add a WebKit API that registers a V8 extension to be loaded into contentmpcomplete@chromium.org2009-07-301-1/+2
* Remove dependencies on the bug-bait V8Proxy::context() API. No behavior change.abarth@chromium.org2009-07-301-2/+2
* Another try at enabling the content script messaging test.mpcomplete@chromium.org2009-07-241-12/+13
* Revert "Fix an issue with unregistering content script contexts."mpcomplete@chromium.org2009-07-221-13/+12
* Fix an issue with unregistering content script contexts.mpcomplete@chromium.org2009-07-221-12/+13
* Don't dispatch the extensions bindings unload event during GC.mpcomplete@chromium.org2009-07-211-12/+26
* Changed the extension.connect() API not to broadcast to all tabs. Added ampcomplete@chromium.org2009-07-201-12/+44
* Retrying this patch. This was already reviewed by mpcomplete and thefinnur@chromium.org2009-07-151-5/+9
* Chrome-side of fixes for content-script messaging.mpcomplete@chromium.org2009-07-141-26/+65
* Make the API to open a message channel symmetric, so it works the same whethe...mpcomplete@chromium.org2009-07-091-29/+0
* Fix some issues with extension messaging:mpcomplete@chromium.org2009-07-021-1/+4
* Refactor extension bindings to share code, avoid exposing hidden variablesmpcomplete@chromium.org2009-06-301-75/+96
* Add notifications for when V8Proxy creates or destroys a V8 Context.mpcomplete@chromium.org2009-06-261-0/+17
* Revert 18765 to try to repair perf regressionjar@chromium.org2009-06-191-25/+6
* Send port-closed notification when a frame with ports unloads.mpcomplete@google.com2009-06-181-6/+25
* Change the extension callback system to work more like events, where we trackmpcomplete@google.com2009-06-101-14/+1
* Revert 17889. It broke the extensions_uitests. And I didn't even get itmpcomplete@google.com2009-06-081-1/+14
* Change the extension callback system to work more like events, where we trackmpcomplete@google.com2009-06-081-14/+1
* BUG=12192rafaelw@chromium.org2009-05-301-3/+1
* Remove executable bit from a bunch of files that shouldn't have it.evan@chromium.org2009-05-111-0/+0
* Only send events to renderers that are listening to an event.Notify browser w...erikkay@google.com2009-05-011-3/+47
* Change extension event bindings to auto-detach events when the window unloads.mpcomplete@google.com2009-04-201-20/+41
* Hook up extension events to the json parser, and change the extension messagempcomplete@google.com2009-04-131-1/+5
* Add aa's Event class to our javascript bindings and use it in our extensionmpcomplete@google.com2009-04-081-0/+119