Remove some weird comments that are not really necessary causing confusion.

Remove some weird comments that are not really necessary causing confusion.
    
BUG=None

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

[atreat, 2014-02-21 19:22:52]

Not sure what is wrong with the bots, but I don't think it is related.

[esprehn, 2014-02-21 19:30:32]

How much of an impact LayoutState has is based on what CSS properties you use
and how much we need to consult the data inside it. You probably need to add
transforms and other things that LayoutState optimize to see the difference.

That comment is weird, we don't need to comment every LayoutStateMaintainer
call...

[atreat, 2014-02-21 19:39:51]

On 2014/02/21 19:30:32, esprehn wrote:
> How much of an impact LayoutState has is based on what CSS properties you use
> and how much we need to consult the data inside it. You probably need to add
> transforms and other things that LayoutState optimize to see the difference.
> 
> That comment is weird, we don't need to comment every LayoutStateMaintainer
> call...

You think I should just take out the comment?  I thought it was saying that
those classes will not take advantage of the LayoutState optimization anyway,
but we should still use LayoutStateMaintainer because LayoutStateDisabler is a
heavier class which is not true.  If RenderMedia and RenderEmbeddedObject can
use the LayoutState optimization, then perhaps the comment should just go...

[esprehn, 2014-02-21 19:51:17]

On 2014/02/21 19:39:51, atreat wrote:
> On 2014/02/21 19:30:32, esprehn wrote:
> > How much of an impact LayoutState has is based on what CSS properties you
use
> > and how much we need to consult the data inside it. You probably need to add
> > transforms and other things that LayoutState optimize to see the difference.
> > 
> > That comment is weird, we don't need to comment every LayoutStateMaintainer
> > call...
> 
> You think I should just take out the comment?  I thought it was saying that
> those classes will not take advantage of the LayoutState optimization anyway,
> but we should still use LayoutStateMaintainer because LayoutStateDisabler is a
> heavier class which is not true.  If RenderMedia and RenderEmbeddedObject can
> use the LayoutState optimization, then perhaps the comment should just go...

The issue is if the media controls elements can use the LayoutState of their
parent, which I think is true. The comment should probably be removed unless you
can prove that they don't work. :)

[atreat, 2014-02-21 21:41:41]

On 2014/02/21 19:51:17, esprehn wrote:
> On 2014/02/21 19:39:51, atreat wrote:
> > On 2014/02/21 19:30:32, esprehn wrote:
> The issue is if the media controls elements can use the LayoutState of their
> parent, which I think is true. The comment should probably be removed unless
you
> can prove that they don't work. :)

Ok, new patch to just remove the comments.

[esprehn, 2014-02-21 22:02:38]

lgtm

[atreat, 2014-02-22 17:09:01]

The CQ bit was checked by adam.treat@samsung.com

[commit-bot: I haz the power, 2014-02-22 17:09:15]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/adam.treat@samsung.com/174343004/100001

[commit-bot: I haz the power, 2014-02-22 21:14:16]

Change committed as 167639