DescriptionRemove CompositingUpdateAfterStyleChange
CompositingUpdateAfterStyleChange does the same thing as
CompositingUpdateAfterCompositingInputChange. There's no reason to have two enums.
Also, I've inlined FrameView::updateCompositingLayersAfterStyleChange because
that function just contained a redundant null check.
BUG=332248
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=175694
Patch Set 1 #
Total comments: 1
Messages
Total messages: 4 (0 generated)
|