See also internal issue 72559941.
translateZ(0) and similar constructs currently trigger composited layers.
Sites do this on purpose to isolate raster and paint costs and improve
caching. However, the memory and per-composited-layer overhead
costs on low-end Android devices likely outweigh the desire to
composite on behalf of developers.
Note that compositing is not required for correctness in this case-
it's a pure performance tradeoff.
Will watch performance metrics after this change to see its impact.
Comment 1 by bugdroid1@chromium.org
, Feb 9 2018