Fix a trace value type in RenderPassDrawQuad.

Fix a trace value type in RenderPassDrawQuad.

gfx::size's trace value type should be dictionary.

Committed: https://crrev.com/97313ec841a23ad5eeb76311e845b8f16fce780f
Cr-Commit-Position: refs/heads/master@{#311157}

[JungJik, 2015-01-12 10:55:48]

jungjik.lee@samsung.com changed reviewers:
+ vmpstr@chromium.org

[JungJik, 2015-01-12 10:55:49]

PTAL
this is for fixing a crash when cc.debug.quad is on.

[danakj, 2015-01-12 18:03:21]

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

[danakj, 2015-01-12 18:03:22]

LGTM

https://codereview.chromium.org/801293003/diff/1/cc/quads/render_pass_draw_qu...
File cc/quads/render_pass_draw_quad.cc (right):

https://codereview.chromium.org/801293003/diff/1/cc/quads/render_pass_draw_qu...
cc/quads/render_pass_draw_quad.cc:102:
value->BeginDictionary("mask_texture_size");
Oof, this is kinda meh. We can surely make a better api on MathUtil to do this,
maybe pass it the string, the variable, and the value, and have it decide the
type internally.

[JungJik, 2015-01-12 23:22:17]

The CQ bit was checked by jungjik.lee@samsung.com

[commit-bot: I haz the power, 2015-01-12 23:23:35]

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

[commit-bot: I haz the power, 2015-01-13 00:28:03]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-01-13 00:28:58]

Patchset 1 (id:??) landed as
https://crrev.com/97313ec841a23ad5eeb76311e845b8f16fce780f
Cr-Commit-Position: refs/heads/master@{#311157}

[JungJik, 2015-01-13 01:04:42]

https://codereview.chromium.org/801293003/diff/1/cc/quads/render_pass_draw_qu...
File cc/quads/render_pass_draw_quad.cc (right):

https://codereview.chromium.org/801293003/diff/1/cc/quads/render_pass_draw_qu...
cc/quads/render_pass_draw_quad.cc:102:
value->BeginDictionary("mask_texture_size");
On 2015/01/12 18:03:22, danakj wrote:
> Oof, this is kinda meh. We can surely make a better api on MathUtil to do
this,
> maybe pass it the string, the variable, and the value, and have it decide the
> type internally.

thanks for the review.
I understand your intention and will file a new patch.