summaryrefslogtreecommitdiffstats
path: root/chrome/browser/extensions/extension_view_unittest.cc
Commit message (Expand)AuthorAgeFilesLines
* 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
generated by cgit v1.1 at 2025-02-08 15:02:36 +0000