Delete DeprecatedDirtyCompositingDuringCompositingUpdate

Delete DeprecatedDirtyCompositingDuringCompositingUpdate

This CL is a bit of a parlor trick, but it seems worthwhile to remove
DeprecatedDirtyCompositingDuringCompositingUpdate.

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

[ojan, 2014-06-11 18:42:04]

Lol. This is what I did in my original patch that you had me undo! So...lgtm. :)

[commit-bot: I haz the power, 2014-06-11 18:43:07]

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

[ojan, 2014-06-11 18:44:47]

https://codereview.chromium.org/334443005/diff/1/Source/core/rendering/compos...
File Source/core/rendering/compositing/RenderLayerCompositor.cpp (right):

https://codereview.chromium.org/334443005/diff/1/Source/core/rendering/compos...
Source/core/rendering/compositing/RenderLayerCompositor.cpp:194:
enableCompositingModeIfNeeded();
Incidentally, if we were to continue to invest in fixing the compositing code, I
think this call should go away entirely. We should only enable composting mode
when we allocate the root compositing layer. Right now we enable it only to
disable it later in some edge cases. That's both silly and means that anywhere
we query the m_compositing bit is getting an incorrect value.

I think we're pretty close to deleting this line now. I've gotten rid of most of
the m_compositing checks. We just need to make sure nothing under updateIfNeeded
queries m_compositing before the stage where we allocate the root compositing
layer.

[abarth-chromium, 2014-06-11 19:20:57]

On 2014/06/11 at 18:44:47, ojan wrote:
> Incidentally, if we were to continue to invest in fixing the compositing code

I'm going to continue fixing the code.  :)

[commit-bot: I haz the power, 2014-06-11 19:39:55]

Change committed as 175977