summaryrefslogtreecommitdiffstats
path: root/chrome/chrome_browser.gypi
diff options
context:
space:
mode:
authorstuartmorgan@chromium.org <stuartmorgan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-03-23 17:46:07 +0000
committerstuartmorgan@chromium.org <stuartmorgan@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-03-23 17:46:07 +0000
commit3773020c131d144f0e0e1d849227b34d7c4cf6e1 (patch)
tree41149e9430a021044a811864c974aed26a89fb9c /chrome/chrome_browser.gypi
parent6ed9b2141d30010e1a0c7055f03cbc726f3bd3a6 (diff)
downloadchromium_src-3773020c131d144f0e0e1d849227b34d7c4cf6e1.zip
chromium_src-3773020c131d144f0e0e1d849227b34d7c4cf6e1.tar.gz
chromium_src-3773020c131d144f0e0e1d849227b34d7c4cf6e1.tar.bz2
Add a temporary flag to enable Core Animation mode for Flash (when possible)
This makes our Mac wmode hack--which prevents Flash from using "accelerated" QuickDraw mode, which is incredibly slow for us, but also prevents Flash 10.1 from using Core Animation in the same cases--conditional based on having both support for Core Animation mode in both Flash and Chromium, and on having a flag. Once we are confident that there are no regressions preventing us from allowing Core Animation by default, the flag will be removed. BUG=38932 TEST=Run with --enable-flash-core-animation and the current Flash 10.1 beta on 10.6; sites like YouTube should have negligable CPU usage. Review URL: http://codereview.chromium.org/1115010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@42356 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome_browser.gypi')
0 files changed, 0 insertions, 0 deletions