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

To amend what hayato said(https://github.com/w3c/webcomponents/issues/184#issuecomment-219905487), we *can* keep a joint session history somewhere, and browser can use it for
back/forward buttons. We don't expose the joint session history to any window.history
interface.

We used to have (implicit?) assumption that history objects in main page/iframes has
history list synced with browser UI's back/forward button,
but in the new world, any `history.go()` in each iframe in shadow DOM is local,
and such local movement doesn't necessarily matches the old world's synced,
linear movement, and there can be multiple possibility of how browser's back/forward
button works.

---
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-219923550