diff options
author | husky@chromium.org <husky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-08-21 19:33:58 +0000 |
---|---|---|
committer | husky@chromium.org <husky@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-08-21 19:33:58 +0000 |
commit | 884f9002d61b445c35f98a033867b282e5d97ace (patch) | |
tree | 6e2885aec630decbf6b117e2f75d07a8c58dd7a5 /chrome/browser/plugin_prefs.cc | |
parent | 4f2c7acdd25fb0eb251c0309921b77feb90998f6 (diff) | |
download | chromium_src-884f9002d61b445c35f98a033867b282e5d97ace.zip chromium_src-884f9002d61b445c35f98a033867b282e5d97ace.tar.gz chromium_src-884f9002d61b445c35f98a033867b282e5d97ace.tar.bz2 |
Call WebFrame::selectRange instead of WebFrame::setSelectionToRange
WebFrame has two nearly-identical methods, selectRange and setSelectionToRange.
setSelectionToRange exits early if the selection isn't editable, but otherwise
behaves the same. It's only used in RenderViewImpl::OnImeConfirmComposition, so
the selection should always be editable.
This patch standardizes on selectRange. I'll remove setSelectionToRange in a
separate WebKit patch.
BUG=143677
TEST=RenderViewImplTest.ImeComposition
Review URL: https://chromiumcodereview.appspot.com/10829420
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152608 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/plugin_prefs.cc')
0 files changed, 0 insertions, 0 deletions