Added the command line flag that enables CSS Shaders: "--enable-css-custom-filter".

Added the command line flag that enables CSS Shaders: "--enable-css-shaders".


BUG=119861
TEST=

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=129598

[greggman, 2012-03-24 04:55:35]

it looks ok to me but you'll need approval from people charge of the various
folders.

sky, PTAL at context/browser/tab_contents/tab_contents
joi, PTAL at content/public/common/content_switches.*
darin, PTAL at context/common/view_messages.h and webkit/glue/webpreferences.*

[darin (slow to review), 2012-03-24 06:24:48]

LGTM

[darin (slow to review), 2012-03-24 06:25:18]

On 2012/03/24 06:24:48, darin wrote:
> LGTM

I think you can just TBR the other reviews.  This is a very straightforward
change.

[Jói, 2012-03-26 12:20:54]

LGTM for content/public.

[Jói, 2012-03-26 12:22:16]

> I think you can just TBR the other reviews.  This is a very straightforward
> change.

+1, TBR for this would have been fine for my part at least.

Cheers,
Jói


On Sat, Mar 24, 2012 at 6:25 AM,  <darin@chromium.org> wrote:
> On 2012/03/24 06:24:48, darin wrote:
>>
>> LGTM
>
>
> I think you can just TBR the other reviews.  This is a very straightforward
> change.
>
> http://codereview.chromium.org/9839073/

[commit-bot: I haz the power, 2012-03-26 16:07:18]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/achicu@adobe.com/9839073/1008

[commit-bot: I haz the power, 2012-03-26 18:45:27]

Try job failure for 9839073-1008 (retry) on win_rel for step "browser_tests".
It's a second try, previously, steps "browser_tests, installer_util_unittests"
failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[achicu, 2012-03-26 18:52:41]

On 2012/03/26 18:45:27, I haz the power (commit-bot) wrote:
> Try job failure for 9839073-1008 (retry) on win_rel for step "browser_tests".
> It's a second try, previously, steps "browser_tests, installer_util_unittests"
> failed.
>
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

I don't think that this is related to my change.

[commit-bot: I haz the power, 2012-03-26 19:02:03]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/achicu@adobe.com/9839073/1008

[commit-bot: I haz the power, 2012-03-26 21:01:04]

Try job failure for 9839073-1008 (retry) on win_rel for step "compile" (clobber
build).
It's a second try, previously, step "compile" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[achicu, 2012-03-26 21:22:07]

The build didn't fail because of my change. What can I do to have this
patch committed anyway?

Thanks,
Alex

On 3/26/12 2:01 PM, "commit-bot@chromium.org" <commit-bot@chromium.org>
wrote:

>Try job failure for 9839073-1008 (retry) on win_rel for step "compile"
>(clobber
>build).
>It's a second try, previously, step "compile" failed.
>http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel
>&number=14077
>
>
>http://codereview.chromium.org/9839073/

[commit-bot: I haz the power, 2012-03-26 21:25:26]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/achicu@adobe.com/9839073/1008

[commit-bot: I haz the power, 2012-03-26 23:36:36]

Try job failure for 9839073-1008 (retry) on win_rel for step "unit_tests"
(clobber build).
It's a second try, previously, step "compile" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2012-03-28 18:48:21]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/achicu@adobe.com/9839073/1008

[commit-bot: I haz the power, 2012-03-28 21:31:10]

Try job failure for 9839073-1008 (retry) on win_rel for step "browser_tests".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2012-03-28 21:49:59]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/achicu@adobe.com/9839073/1008

[commit-bot: I haz the power, 2012-03-28 21:50:02]

Can't apply patch for file AUTHORS.
While running patch -p1 --forward --force;
patching file AUTHORS
Hunk #1 FAILED at 171.
1 out of 1 hunk FAILED -- saving rejects to file AUTHORS.rej

[commit-bot: I haz the power, 2012-03-28 21:51:55]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/achicu@adobe.com/9839073/1008

[commit-bot: I haz the power, 2012-03-28 21:51:58]

Can't apply patch for file AUTHORS.
While running patch -p1 --forward --force;
patching file AUTHORS
Hunk #1 FAILED at 171.
1 out of 1 hunk FAILED -- saving rejects to file AUTHORS.rej

[commit-bot: I haz the power, 2012-03-28 22:59:22]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/achicu@adobe.com/9839073/25001

[commit-bot: I haz the power, 2012-03-29 02:24:06]

Try job failure for 9839073-25001 (retry) on win_rel for step "browser_tests".
It's a second try, previously, step "browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2012-03-29 04:20:54]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/achicu@adobe.com/9839073/25001

[commit-bot: I haz the power, 2012-03-29 07:07:22]

Try job failure for 9839073-25001 (retry) on win_rel for step "browser_tests".
It's a second try, previously, steps "ui_tests, browser_tests" failed.
http://build.chromium.org/p/tryserver.chromium/buildstatus?builder=win_rel&nu...

[commit-bot: I haz the power, 2012-03-29 07:08:46]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/achicu@adobe.com/9839073/25001

[commit-bot: I haz the power, 2012-03-29 09:02:31]

Change committed as 129598