Rename AncestorDependentProperties to CompositingInputs

Rename AncestorDependentProperties to CompositingInputs

This state on RenderLayer is specific to the compositor. The name
AncestorDependentProperties hasn't aged well. In other places, we call these
CompositingInputs, which seems more appropriate.

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=175925

[chrishtr, 2014-06-10 20:53:27]

lgtm

[commit-bot: I haz the power, 2014-06-10 20:54:26]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/abarth@chromium.org/322163003/20001

[esprehn, 2014-06-10 21:04:26]

lgtm, might have been nice to go with setNeedsCompositingInputRecalc() to match
style recalc and such. Having "To" in the middle always reads weird to me, but
this is fine.

[abarth-chromium, 2014-06-10 21:11:27]

On 2014/06/10 at 21:04:26, esprehn wrote:
> lgtm, might have been nice to go with setNeedsCompositingInputRecalc() to
match style recalc and such. Having "To" in the middle always reads weird to me,
but this is fine.

Done.

[abarth-chromium, 2014-06-10 21:11:39]

The CQ bit was checked by abarth@chromium.org

[commit-bot: I haz the power, 2014-06-10 21:11:50]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/abarth@chromium.org/322163003/40001

[ojan, 2014-06-10 21:37:09]

On 2014/06/10 at 21:11:27, abarth wrote:
> On 2014/06/10 at 21:04:26, esprehn wrote:
> > lgtm, might have been nice to go with setNeedsCompositingInputRecalc() to
match style recalc and such. Having "To" in the middle always reads weird to me,
but this is fine.
> 
> Done.

lies!

[abarth-chromium, 2014-06-10 21:54:14]

On 2014/06/10 at 21:37:09, ojan wrote:
> On 2014/06/10 at 21:11:27, abarth wrote:
> > On 2014/06/10 at 21:04:26, esprehn wrote:
> > > lgtm, might have been nice to go with setNeedsCompositingInputRecalc() to
match style recalc and such. Having "To" in the middle always reads weird to me,
but this is fine.
> > 
> > Done.
> 
> lies!

Why, because I made it setNeedsCompositingInputsUpdate rather than
setNeedsCompositingInputRecalc ?

[esprehn, 2014-06-10 21:55:05]

On 2014/06/10 at 21:54:14, abarth wrote:
> On 2014/06/10 at 21:37:09, ojan wrote:
> > On 2014/06/10 at 21:11:27, abarth wrote:
> > > On 2014/06/10 at 21:04:26, esprehn wrote:
> > > > lgtm, might have been nice to go with setNeedsCompositingInputRecalc()
to match style recalc and such. Having "To" in the middle always reads weird to
me, but this is fine.
> > > 
> > > Done.
> > 
> > lies!
> 
> Why, because I made it setNeedsCompositingInputsUpdate rather than
setNeedsCompositingInputRecalc ?

I don't really care about the recalc part. :)

[commit-bot: I haz the power, 2014-06-10 22:22:24]

Change committed as 175925

[ojan, 2014-06-11 01:58:02]

On 2014/06/10 at 21:54:14, abarth wrote:
> On 2014/06/10 at 21:37:09, ojan wrote:
> > On 2014/06/10 at 21:11:27, abarth wrote:
> > > On 2014/06/10 at 21:04:26, esprehn wrote:
> > > > lgtm, might have been nice to go with setNeedsCompositingInputRecalc()
to match style recalc and such. Having "To" in the middle always reads weird to
me, but this is fine.
> > > 
> > > Done.
> > 
> > lies!
> 
> Why, because I made it setNeedsCompositingInputsUpdate rather than
setNeedsCompositingInputRecalc ?

I didn't see the first version of the patch. I didn't really mean this as a
serious comment though. Sorry for the confusion.

[abarth-chromium, 2014-06-11 04:12:36]

On 2014/06/11 at 01:58:02, ojan wrote:
> I didn't see the first version of the patch. I didn't really mean this as a
serious comment though. Sorry for the confusion.

No worries :)