summaryrefslogtreecommitdiffstats
path: root/chrome/browser/extensions/extension_view_unittest.cc
Commit message (Expand)AuthorAgeFilesLines
* Disable extensions in incognito mode.mpcomplete@google.com2009-06-111-140/+0
* part 2 of dragging change: reordering, but not persistingerikkay@google.com2009-06-101-7/+7
* Display extension processes in task manager.phajdan.jr@chromium.org2009-06-061-1/+1
* Headers cleanup in chrome/browser/phajdan.jr@chromium.org2009-06-031-0/+1
* Remove unused code from ExtensionsService.mpcomplete@google.com2009-05-261-1/+1
* Remove executable bit from a bunch of files that shouldn't have it.evan@chromium.org2009-05-111-0/+0
* Resurrect ExtensionProcessManager. Move the code for starting extensionmpcomplete@google.com2009-05-061-1/+3
* Create a separate UI surface for extensions (bottom shelf) and remove them fr...erikkay@google.com2009-05-061-0/+30
* Refactor ExtensionView to support a UI-less extension instance.mpcomplete@google.com2009-04-291-11/+11
* Implement tabs.createWindow extension api call. Required: (a) new RVHDelegate...rafaelw@chromium.org2009-04-281-0/+6
* Remove ExtensionProcessManager and move its functionality ontompcomplete@google.com2009-04-161-5/+3
* Add JsonSchema-based validation for the tab APIs.aa@chromium.org2009-04-141-1/+1
* Revert "Add JsonSchema-based validation for the tab APIs."aa@chromium.org2009-04-141-1/+0
* Add JsonSchema-based validation for the tab APIs.aa@chromium.org2009-04-141-0/+1
* Hook up extension events to the json parser, and change the extension messagempcomplete@google.com2009-04-131-0/+4
* Hook up a bit more plumbing to ExtensionView which should allow popup windows...erikkay@google.com2009-04-131-3/+4
* Introducing ExtensionProcessManager. This manages the ExtensionViews tompcomplete@google.com2009-04-091-3/+8
* Try one more time to check in http://codereview.chromium.org/60112aa@chromium.org2009-04-081-56/+7
* Revert "Implement chromium.self in content scripts..."aa@chromium.org2009-04-071-7/+56
* Implement chromium.self in content scripts, so that developers don'taa@chromium.org2009-04-071-56/+7
* Move code to allow dns queries (and accompanyingaa@chromium.org2009-04-031-13/+0
* Prevent making real DNS lookups by chrome tests.phajdan.jr@chromium.org2009-03-271-0/+14
* Initial rev at a message passing API for extensions. So far, only passingmpcomplete@google.com2009-03-231-3/+3
* Revert change 12247 because it created a lot of memory regressionsnsylvain@chromium.org2009-03-221-7/+56
* Committing issue 39299:aa@chromium.org2009-03-211-56/+7
* Allow multiple toolstrips in an extension.aa@chromium.org2009-03-211-1/+1
* Disable single-process mode in ExtensionViewTest, to see if it's causingmpcomplete@google.com2009-03-131-3/+3
* Run ExtensionViewTest in single-process mode to try to make it less flaky.mpcomplete@google.com2009-03-121-0/+3
* Reverting 11467.mpcomplete@google.com2009-03-111-3/+0
* Try to make ExtensionViewTest less flaky by running it in single-process mode.mpcomplete@google.com2009-03-111-0/+3
* Re-enable ExtensionViewTest.mpcomplete@google.com2009-03-101-3/+1
* Extra disable ExtensionViewTest.mpcomplete@google.com2009-03-101-0/+2
* Disable ExtensionViewTest.Index while I fix it.mpcomplete@google.com2009-03-101-1/+1
* Unrevert 11294.mpcomplete@google.com2009-03-101-1/+1
* Fix build break.mpcomplete@google.com2009-03-061-1/+2
* Fix Purify UMR and MLK due to ExtensionViewTest:mpcomplete@google.com2009-03-061-0/+4
* Try #2 of "make JavaScript alerts reflect the URL of the frame they came from,brettw@chromium.org2009-03-051-0/+1
* Reverting 11002.brettw@chromium.org2009-03-051-1/+0
* Make JavaScript alerts reflect the URL of the frame they came from, not thebrettw@chromium.org2009-03-051-0/+1
* Fix ExtensionViewTest and reenable it.mpcomplete@google.com2009-03-031-6/+30
* Disable the ExtensionViewTest while I investigate why it's hanging on thempcomplete@google.com2009-02-271-1/+1
* Prototype extension process. This is a proof of concept, with a lot ofmpcomplete@google.com2009-02-271-0/+108