summaryrefslogtreecommitdiffstats
path: root/sandbox/tools
diff options
context:
space:
mode:
authorhbono@chromium.org <hbono@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-02-12 04:57:14 +0000
committerhbono@chromium.org <hbono@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-02-12 04:57:14 +0000
commit03bd6648b11dd3d915103f847feed28d0af4c7c2 (patch)
tree85abd3b835fc6509aa935c673092860b9d4bdda9 /sandbox/tools
parent2255d61195136acb02d4b6a1e4b70977975ee716 (diff)
downloadchromium_src-03bd6648b11dd3d915103f847feed28d0af4c7c2.zip
chromium_src-03bd6648b11dd3d915103f847feed28d0af4c7c2.tar.gz
chromium_src-03bd6648b11dd3d915103f847feed28d0af4c7c2.tar.bz2
Add the first unit-test that tests our IME backend.
This change is the first unit-test that tests our IME backend in the RenderWidget class. Thanks to the unit-test framework for the RenderView class created by Carlos and Brett, we can now implement this unit test. (I'm not sure I use this framework correctly, though. Please blame me if I use it improperly.) Currently, this IME test just tests if our IME code can properly activate (or de-activate) IMEs for an <input> element and the initial position of a candidate window. I'm going to add more practical cases to this test. Review URL: http://codereview.chromium.org/20014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9648 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sandbox/tools')
0 files changed, 0 insertions, 0 deletions