Re: [css-containment] For what problems is CSS Containment the best solution?

On Tue, Feb 18, 2014 at 12:34 PM, Robert O'Callahan
<robert@ocallahan.org> wrote:
> I was thinking about the best way to implement CSS rendering of large data
> sets and wrote my thoughts down in blog (and demo) form:
> http://robert.ocallahan.org/2014/02/implementing-virtual-widgets-on-web.html
> In summary, for maximum scalability you want to dynamically create and
> recycle DOM elements so that the size of your DOM is proportional to the
> amount of visible data, not the amount of data available. This can be
> implemented reasonably well on the Web platform, though there are a couple
> of small API extensions that would make it work better. If you take this
> approach, CSS Containment is not needed or even particularly helpful.
>
> So, for what use-cases is CSS Containment a better solution than such
> DOM-recycling techniques? I don't know.

Even when you're using DOM-recycling, tweaking things inside each
"component" can cause unnecessary layout and paint dirtying outside of
it.

This is quite possible to fix, in various ways, but one of the
motivations for 'contain' is to make a single *predictable* entry
point for "isolate this as much as possible", rather than requiring an
author to lean and remember the N things that have to be set
correctly, and which the lack of any one can cause perf regression.

~TJ

Received on Wednesday, 5 March 2014 00:35:15 UTC