summaryrefslogtreecommitdiffstats
path: root/content/browser/renderer_host/touch_event_queue.h
diff options
context:
space:
mode:
authormpearson@chromium.org <mpearson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-07-19 23:40:25 +0000
committermpearson@chromium.org <mpearson@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2013-07-19 23:40:25 +0000
commit518024c161921db45e32d6eb4f177a91888ade74 (patch)
tree041ec4d449d62a16a39b619925f1e50faf132267 /content/browser/renderer_host/touch_event_queue.h
parent4abbcbb625743e9f6df90c520265555f03fea3c1 (diff)
downloadchromium_src-518024c161921db45e32d6eb4f177a91888ade74.zip
chromium_src-518024c161921db45e32d6eb4f177a91888ade74.tar.gz
chromium_src-518024c161921db45e32d6eb4f177a91888ade74.tar.bz2
Omnibox: Change |inline_autocomplete_offset| to |inline_autocompletion|
This makes things easier to understand. No more messy indexing into |fill_into_edit|. No more wondering whether inline_autocomplete_offset == fill_into_edit.length() is equivalent to inline_autocomplete_offset == string16::npos (Answer: currently equivalent.) Also, it's probably easier in the future to make distinctions between |fill_into_edit| and the inline completion. For instance, we may want one to have a trailing slash and the other not to under certain conditions. The previous code restricted our ability to do this. BUG= TBR=estade ( for chrome/browser/resources/omnibox/omnibox.js ) Review URL: https://chromiumcodereview.appspot.com/19197005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@212693 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/browser/renderer_host/touch_event_queue.h')
0 files changed, 0 insertions, 0 deletions