- From: T.J. Crowder <tj@crowdersoftware.com>
- Date: Fri, 16 Mar 2012 09:23:12 +0100
- To: John J Barton <johnjbarton@johnjbarton.com>
- Cc: public-html-comments@w3.org
- Message-ID: <CAH65x-x2-FR4FGQyYRsqgeDscXNoAwxRUv9OYSaJ7fNUzkNCNw@mail.gmail.com>
FWIW, I would suggest that if the spec is ambiguous on it, it should be updated such that the ambiguity is resolved in favor of the behavior you're seeing being a bug. IMHO, the properties you've set on the iframe's window object should be retained. -- T.J. Crowder Independent Software Engineer tj@crowdersoftware.com On 16 March 2012 05:31, John J Barton <johnjbarton@johnjbarton.com> wrote: > The HTML5 spec has: > > "Removing an iframe from a Document does not cause its browsing > context to be discarded. . Indeed, an iframe's browsing context can > survive its original parent Document if its iframe is moved to another > Document." > > To me this statement is ambiguous, since we don't know what 'not ... > discarded' or "survive' means. Does 'survive' mean that the values in > the browsing context remain intact? If the context were to say issue > setInterval based computations, would these continue? > > I am doing the equivalent of: > document.body.appendChild(iframe); > // sometime after the load event: > anotherElement.appendChild(iframe); > > The second appendChild should remove the iframe element from the > document and then insert it under anotherElement. And it does. > > However the properties of the window object that I set are not retained. > > If I look at the value of iframe.contentWindow.editorInterface before > the second appendChild(), it has the values I defined in the iframe. > > If I look at the value after the second appendChild() it is 'undefined'. > > I can't tell from the spec if this is a bug or not. Do we know? > > jjb > >
Received on Friday, 16 March 2012 08:24:02 UTC