diff options
author | jamesr@chromium.org <jamesr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-05-15 21:18:52 +0000 |
---|---|---|
committer | jamesr@chromium.org <jamesr@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-05-15 21:18:52 +0000 |
commit | 799fd73a655c9c3f91a1c14618bdc27126dba152 (patch) | |
tree | d349ce60fdfbdb08abfa3c2df072cb7bc783bba7 /WATCHLISTS | |
parent | 891109be775c4ed0261c7fb8392840ddee7becfa (diff) | |
download | chromium_src-799fd73a655c9c3f91a1c14618bdc27126dba152.zip chromium_src-799fd73a655c9c3f91a1c14618bdc27126dba152.tar.gz chromium_src-799fd73a655c9c3f91a1c14618bdc27126dba152.tar.bz2 |
Move webkit/compositor_bindings into webkit/renderer
The compositor bindings for WebKit should only be used in a render process or in
webkit_support for DumpRenderTree or webkit_unit_tests. It's never used in a
browser process. This moves the bindings code under webkit/renderer/ so we can
enforce this via DEPS rules.
The path is unfortunately a bit awkward. Once we drop DumpRenderTreeSupport and
figure out a way to deal with webkit_unit_tests, we can move the bindings into
content/renderer/gpu/ since they'll only be used by the content embedding.
BUG=239107
TBR=piman@chromium.org
Review URL: https://codereview.chromium.org/14651027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@200350 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'WATCHLISTS')
-rw-r--r-- | WATCHLISTS | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -113,7 +113,7 @@ }, 'cc': { 'filepath': 'cc/|'\ - 'webkit/compositor_bindings/|'\ + 'webkit/renderer/compositor_bindings/|'\ 'content/common/cc_messages' }, 'chrome_frame': { |