summaryrefslogtreecommitdiffstats
path: root/chrome/worker/worker_uitest.cc
diff options
context:
space:
mode:
authorjeremy@chromium.org <jeremy@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-04-29 14:06:14 +0000
committerjeremy@chromium.org <jeremy@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-04-29 14:06:14 +0000
commitbc0c3ba245f12d916dbf028cee9a602bda2550f9 (patch)
tree348362d01cb7eb1bab1e4ff83ccaab3cb4fc1381 /chrome/worker/worker_uitest.cc
parentc7189e191b90798715edcdf8b2edaa2c0c29f3cd (diff)
downloadchromium_src-bc0c3ba245f12d916dbf028cee9a602bda2550f9.zip
chromium_src-bc0c3ba245f12d916dbf028cee9a602bda2550f9.tar.gz
chromium_src-bc0c3ba245f12d916dbf028cee9a602bda2550f9.tar.bz2
Cleanup: Rename OnLoadFont->OnPreCacheFont
I'm working on a Mac specific change where we'll need an IPC message to load a font and pass the font data back to the renderer process. To prevent confusion this CL preemptively renames a Windows message which actually causes a font to be cached by the browser. The distinction between these two operations is subtle but I thought it best to try to prevent future confusion by making sure the IPC messages don't have similar names. BUG=None TEST=None Review URL: http://codereview.chromium.org/1805002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@45931 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/worker/worker_uitest.cc')
0 files changed, 0 insertions, 0 deletions