- From: Anne van Kesteren <annevk@opera.com>
- Date: Wed, 18 Apr 2012 17:46:38 +0200
- To: "Dimitri Glazkov" <dglazkov@chromium.org>, "Henri Sivonen" <hsivonen@iki.fi>
- Cc: public-webapps <public-webapps@w3.org>, "Adam Barth" <w3c@adambarth.com>, "Ian Hickson" <ian@hixie.ch>, "Rafael Weinstein" <rafaelw@google.com>, "Erik Arvidsson" <arv@google.com>, "Yehuda Katz" <wycats@gmail.com>
On Wed, 18 Apr 2012 16:49:55 +0200, Henri Sivonen <hsivonen@iki.fi> wrote: > When implementing this, making embedded content inert is probably the > most time-consuming part and just using a document fragment as a > wrapper isn't good enough anyway, since for example img elements load > their src even when not inserted into the DOM tree. Currently, Gecko > can make imbedded content inert on a per-document basis. This > capability is used for documents returned by XHR, createDocument and > createHTMLDocument. It looks like the template proposal will involve > computing inertness from the ancestor chain (<template> ancestor or > DocumentFragment marked as inert as an ancestor). It's unclear to me > what the performance impact will be. FYI, now there's <dialog> and a global inert="" attribute so if those features stay <template> should presumably just hook into them. -- Anne van Kesteren http://annevankesteren.nl/
Received on Wednesday, 18 April 2012 15:47:28 UTC