Handle cases when locked subtree is too large to efficiently cache

[chrishtr]

Consider a locked element which is much larger than the viewport, or far offscreen. We should have the ability to avoid locking too much memory to store the cached rendering output for such elements. Perhaps checkerboarding, like we do for async images or too-tall scrollable areas, suffices?