Re: [w3c/webcomponents] <iframe> and the History API (#184)

A *joint session history* was a design mistake, right?

In other words, if we are allowed to design iframes from scratch, we never let iframes have such a behavior. Is my understanding correct?

I thought that there is a use case of a joint session history, but I do not see any use case in this thread.

If so, I am okay to *re-design* iframes for shadow trees. Forget joint session history at all. No new attribute. No customizable.

For the compatibility, we will have *legacy* iframes in a document tree, which have a joint session history.


---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/184#issuecomment-214146422

Received on Monday, 25 April 2016 05:47:43 UTC