chromium_src.git - central chromium sources

	Commit message (Collapse)	Author	Age	Files	Lines
*	FBTF: Move more ctors/dtors from headers to implementation.	erg@google.com	2010-09-01	1	-0/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	- Adding/Moving dtors of objects that have CancelableRequestConsumers shaves three megs off browser.a. - Adding/Moving dtors of objects that have ScopedRunnableMethodFactories only shaved 100k off browser.a/renderer.a. - Adding/Moving dtors of objects that used some form of base::*Timer<> was negligible; there were only a few classes that had a Timer but had a ctor/dtor in the header after the previous cleanups. BUG=none TEST=compiles Review URL: http://codereview.chromium.org/3278006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@58192 0039d316-1c4b-4281-b951-d872f2087c98
*	Don't re-run content scripts on fragment navigations.	asargent@chromium.org	2010-02-24	1	-4/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This regression was inadvertently introduced by a fix to make executeScript run after a fragment navigation (bug 29541). That patch was: http://codereview.chromium.org/566041 The problem is that on frame navigations (didChangeLocationWithinPage), we end up creating a new UserScriptIdleScheduler, so this patch keeps track of the previous has_run state and propagates that to the new UserScriptIdleScheduler. BUG=35924 TEST=Steps to verify are outlined in bug report Review URL: http://codereview.chromium.org/646017 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@39939 0039d316-1c4b-4281-b951-d872f2087c98
*	Make sure chrome.tab.executeScript runs in fragment-navigated frames.	asargent@chromium.org	2010-02-08	1	-0/+4
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	BUG=29541 TEST=Install a test extension that has a browser action that uses executeScript when you click on it to do something in the current tab like call alert (the bug report has one). Then: 1) navigate to any site like http://www.google.com/ 2) Add #foo to the end of url and hit enter. 3) Hit browser action button. 4) You should see the results. Review URL: http://codereview.chromium.org/566041 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@38368 0039d316-1c4b-4281-b951-d872f2087c98
*	Fix a bug where content scripts would get run twice in some cases.	mpcomplete@chromium.org	2009-12-09	1	-2/+7
\| \| \| \| \| \| \| \|	BUG=29644 Review URL: http://codereview.chromium.org/466079 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@34122 0039d316-1c4b-4281-b951-d872f2087c98
*	Re-commit "Add new user script injection point:	aa@chromium.org	2009-11-03	1	-0/+47
\| \| \| \| \| \| \| \| \| \| \|	document_idle." Original code review: http://codereview.chromium.org/339064 BUG=26126 TBR=rafaelw@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@30796 0039d316-1c4b-4281-b951-d872f2087c98
*	Revert r30784	aa@chromium.org	2009-11-03	1	-47/+0
\| \| \| \| \| \|	TBR=rafaelw@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@30787 0039d316-1c4b-4281-b951-d872f2087c98
*	Add new user script injection point "document_idle" and make it the default.	aa@chromium.org	2009-11-03	1	-0/+47
	Semantically, document-idle means "when the DOM is ready and layout has been idle for awhile", or more loosely, "as soon as we get around to it". Right now this uses a simple heuristic. It injects scripts 200ms after DOMContentLoaded, or immediately after onload, whichever happens first. BUG=26126 TEST=Manual. Extensions with content scripts should work. Review URL: http://codereview.chromium.org/339064 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@30784 0039d316-1c4b-4281-b951-d872f2087c98