chromium_src.git - central chromium sources

	Commit message (Collapse)	Author	Age	Files	Lines
*	Change chrome:// to chrome-ui://, fix up one chrome-resource:// reference.	glen@chromium.org	2009-01-29	1	-1/+1
\| \| \| \| \| \|	Review URL: http://codereview.chromium.org/18175 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8896 0039d316-1c4b-4281-b951-d872f2087c98
*	render_* work.	jrg@chromium.org	2009-01-27	1	-2/+3
\| \| \| \| \| \|	Review URL: http://codereview.chromium.org/18650 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8732 0039d316-1c4b-4281-b951-d872f2087c98
*	Factor out the message sink from MockRenderThread to a separate class. I will be	brettw@chromium.org	2009-01-17	1	-6/+6
\| \| \| \| \| \| \|	using this in a RenderView test in the future. Review URL: http://codereview.chromium.org/18326 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8255 0039d316-1c4b-4281-b951-d872f2087c98
*	First pass as implementing the greasemonkey API. This patch	aa@chromium.org	2009-01-17	1	-1/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	includes a javascript file with stubbed versions of all the greasemoney API methods as well as changes to the Greasemonkey slave to inject this javascript file along with other user scripts into the page.I also have a userscript I'm using for the unit testing of the API methods. I don't think there is a good place for it in the chrome tree (if there is I'd like to know), but you can view it here: http://skrul.com/greasemonkey/test.user.js Right now all the tests fail except for testLog and testUnsafeWindow. Review URL: http://codereview.chromium.org/18183 Patch from Steve Krulewitz <skrulx@gmail.com>. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8247 0039d316-1c4b-4281-b951-d872f2087c98
*	Refactor the render widget unittest so it can be reused to create a render view	brettw@chromium.org	2009-01-05	1	-0/+128
	unit test. Change the mock render thread to save all IPC messages it is asked to send so that tests can verify that the correct ones were sent. There are some new functions that support this checking. Plumb the form state change notification through the render view so that we will correctly update the form state to the browser. Write two RenderView unit tests. One arbitrarily tests OnLoadAlternateHTMLText which I used as a testcase for my testing framework. The other tests the above form state change notification. I had to expose the timeout of this message through the RenderView API so that the test can change it. Review URL: http://codereview.chromium.org/16482 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7549 0039d316-1c4b-4281-b951-d872f2087c98