Certain CCSettings were made global to allow them to be accessed by a LayerChromium that had not yet been added to the tree. This is unfortunate, and it also turns out to be unnecessary. The setting can be plumbed to GraphicsLayerChromium, who can do the check. This depends on a chromium patch to prepare for the change.
Created attachment 148006 [details] Patch I'm very sorry for the churn, but I think that this approach will end up being much simpler and safer than the old one. This patch is essentially a revert of 88384, but please note the changes to RenderLayerCompositor and RenderLayerBacking for the new plumbing.
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
Comment on attachment 148006 [details] Patch Attachment 148006 [details] did not pass chromium-ews (chromium-xvfb): Output: http://queues.webkit.org/results/12967803
Comment on attachment 148006 [details] Patch There is too much happening in this bug. I will split it up.
Created attachment 148015 [details] Patch
Created attachment 150664 [details] Patch
Comment on attachment 150664 [details] Patch I don't think modifying the cross-platform GraphicsLayer API for this chromium-specific concern makes sense.