diff options
| author | skanuj@chromium.org <skanuj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-19 06:33:30 +0000 |
|---|---|---|
| committer | skanuj@chromium.org <skanuj@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-19 06:33:30 +0000 |
| commit | 5408dd86637ca2a5d90b65d32d5bd3bc54c8bbbd (patch) | |
| tree | 49134ff61d9d715b569ed6c45ea303400532bb97 /ipc/ipc_channel.h | |
| parent | 0f0f61020799e2e7350bfdfbb71105c7b1a73a62 (diff) | |
| download | chromium_src-5408dd86637ca2a5d90b65d32d5bd3bc54c8bbbd.zip chromium_src-5408dd86637ca2a5d90b65d32d5bd3bc54c8bbbd.tar.gz chromium_src-5408dd86637ca2a5d90b65d32d5bd3bc54c8bbbd.tar.bz2 | |
Fix rendering of matches with associated keyword match
The associated keyword match and the base match can both be rendered at the same
time for animaiton. My previous CL
(https://codereview.chromium.org/171153004/diff/520001/chrome/browser/ui/views/omnibox/omnibox_result_view.cc)
got that wrong, and caused the linked bugs.
TODO: I can look into caching gfx::RenderText objects for the match and the
keyword match. But the older implementation didn't cache them. I am sending the
fix early to close the regression bugs soon.
BUG=347867,349147
TBR=msw@chromium.org
Review URL: https://codereview.chromium.org/192443007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@257876 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'ipc/ipc_channel.h')
0 files changed, 0 insertions, 0 deletions