cc: Leave using_image capability as false when using software.

cc: Leave using_image capability as false when using software.

The value of this currently doesn't matter when using software.

BUG=418553
R=piman@chromium.org

Committed: https://crrev.com/c1e6e106f35db2ece6bacb6922f9271b47cdcf02
Cr-Commit-Position: refs/heads/master@{#297434}

[danakj, 2014-09-30 14:02:16]

danakj@chromium.org changed reviewers:
+ danakj@chromium.org

[danakj, 2014-09-30 14:02:16]

https://codereview.chromium.org/615953002/diff/1/cc/output/delegating_rendere...
File cc/output/delegating_renderer.cc (right):

https://codereview.chromium.org/615953002/diff/1/cc/output/delegating_rendere...
cc/output/delegating_renderer.cc:48: capabilities_.using_image = false;
or just leave it as the default? is that the same thing?

[danakj, 2014-09-30 14:04:42]

https://codereview.chromium.org/195733010 claims this is set true to avoid a
copy, can you comment on that?

[reveman, 2014-09-30 14:44:10]

On 2014/09/30 14:04:42, danakj wrote:
> https://codereview.chromium.org/195733010 claims this is set true to avoid a
> copy, can you comment on that?

That was only true when we were using the same rasterizer implementation in
software and emulating this extension inside the ResourceProvider. Since
https://codereview.chromium.org/602493003 we have an explicit rasterizer for
software and no emulation of this extension in ResourceProvider. This field
should really have changed to false as part of that change.

[danakj, 2014-09-30 15:19:59]

Ok thanks. Just remove it instead of = false, and LGTM

[reveman, 2014-09-30 15:26:10]

On 2014/09/30 15:19:59, danakj wrote:
> Ok thanks. Just remove it instead of = false, and LGTM

Done

[reveman, 2014-09-30 15:26:15]

The CQ bit was checked by reveman@chromium.org

[commit-bot: I haz the power, 2014-09-30 15:27:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/615953002/20001

[commit-bot: I haz the power, 2014-09-30 15:30:16]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-09-30 15:30:19]

Try jobs failed on following builders:
  mac_gpu on tryserver.chromium.gpu
(http://build.chromium.org/p/tryserver.chromium.gpu/builders/mac_gpu/builds/62513)
  win8_chromium_rel on tryserver.chromium.win
(http://build.chromium.org/p/tryserver.chromium.win/builders/win8_chromium_rel...)

[reveman, 2014-09-30 15:41:15]

The CQ bit was checked by reveman@chromium.org

[commit-bot: I haz the power, 2014-09-30 15:42:25]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/615953002/20001

[commit-bot: I haz the power, 2014-09-30 16:34:33]

Committed patchset #2 (id:20001) as 87472144c3db05f05a04a0f4d3c0b5b797de548f

[commit-bot: I haz the power, 2014-09-30 16:35:05]

Patchset 2 (id:??) landed as
https://crrev.com/c1e6e106f35db2ece6bacb6922f9271b47cdcf02
Cr-Commit-Position: refs/heads/master@{#297434}