From code review 677650:
flackr: Do we need mutable properties at all after compositor worker goes away?
petermayo: property_trees_builder still references them.
flackr: But we don't ever set them - they were the way that we communicated which properties we had constructed compositor proxies of on the main thread, but since CompositorProxy has been removed they will always be MutableProperty::kNone so we can remove all of this code.
We could DCHECK(mutable_properties==MutableProperty::kNone) or remove the code and check that the tests pass.
Comment 1 by schenney@chromium.org
, Sep 26 2017