diff options
author | agl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-25 21:25:31 +0000 |
---|---|---|
committer | agl@chromium.org <agl@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-25 21:25:31 +0000 |
commit | 22a27de7ddd22505f5f281d2fe90a124b7d6ecf0 (patch) | |
tree | be34167345b2c3871c783cca9e16aefa0da1d4bb /DEPS | |
parent | e1b1a5fa61da772666bf58632979776f0651c981 (diff) | |
download | chromium_src-22a27de7ddd22505f5f281d2fe90a124b7d6ecf0.zip chromium_src-22a27de7ddd22505f5f281d2fe90a124b7d6ecf0.tar.gz chromium_src-22a27de7ddd22505f5f281d2fe90a124b7d6ecf0.tar.bz2 |
Linux: plumb fontconfig call out to the sandbox host.
This is hopefully the last step before our renderers can run cleanly
in a chroot.
WebKit needs to be able to ask for the correct font to use in the case
that the current font doesn't include glyphs for certain code points.
Currently we make a fontconfig call in our WebKit port to handle this.
This patch changes this so that the call is sent our via
ChromiumBridge. Since we are at ChromiumBridge, we could make a sync
IPC to the browser. However, fontconfig is a single threaded library
and we are already using it on the UI thread in the browser, so the
sync IPC would have to terminate on the UI thread. Even if this
doesn't deadlock, it causes huge spikes in latency.
So, instead, we send the IPC to the sandbox host process which is
already setup to handle fontconfig requests from Skia. See:
http://code.google.com/p/chromium/wiki/LinuxSandboxIPC
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@19287 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'DEPS')
-rw-r--r-- | DEPS | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1,7 +1,7 @@ vars = { "webkit_trunk": "http://svn.webkit.org/repository/webkit/trunk", - "webkit_revision": "45176", + "webkit_revision": "45191", } |