W3C home > Mailing lists > Public > public-html@w3.org > April 2015

Document persistence for iframes when the node is moved in the DOM

From: Lewis, Eric <eric.lewis@nytimes.com>
Date: Mon, 13 Apr 2015 10:58:56 -0400
Message-ID: <CANSkH2qO7LGvR2ZEhb6-+NcxChRwaYnwiZyOPgc88zvg3En=CQ@mail.gmail.com>
To: public-html@w3.org
Hi all,

I have long understood that iframes "reload" when being moved around the
DOM (i.e https://dl.dropboxusercontent.com/u/1062618/document-bye.mp4).
This weekend I went down the rabbit hole on this topic.

I believe this "reload" is a perceptual reload, and what is going on behind
the scenes is a fresh document being created for the iframe.

James Graham mentioned to me in the WHATWG IRC room that this is a browser
implementation, and that any user-perceivable behavior should be codified
into spec.

This is a persistent issue for web developers
<https://www.google.com/search?q=iframe+reload+dom+move&oq=iframe+re&aqs=chrome.0.69i59j0j69i57j0l3.1647j0j7&sourceid=chrome&es_sm=91&ie=UTF-8>,
and make iframes a leaky abstraction. I request that iframes persist their
document when moved around the DOM.

Eric Lewis
Intrepid Web Developer, Blogs Team
The New York Times
620 Eighth Avenue, 8th Floor
New York, NY 10018
Office: (212) 556-2081
Cell: (610) 715-8560
Received on Monday, 13 April 2015 14:59:44 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:16:43 UTC