W3C home > Mailing lists > Public > www-style@w3.org > February 2014

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

From: Robert O'Callahan <robert@ocallahan.org>
Date: Wed, 19 Feb 2014 09:34:14 +1300
Message-ID: <CAOp6jLbuk-em1oE0wuRhj4eiNujaz9AdvPzsh0ieCwxXBVM80g@mail.gmail.com>
To: www-style <www-style@w3.org>
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.

Rob
-- 
Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w
Received on Tuesday, 18 February 2014 20:34:42 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:19 UTC