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

@smaug---- so I guess the problem is all the state exposed on `History`? If we did not expose that, would we have to expose it somehow on `ShadowRoot`? That each gets its own history? Presumably defaulting to no history at all for v1?

That kind of approach makes sense if you don't want to influence your container, but if you're a simple layout component that breaks expectations. Not sure if there's a good answer here. (We could make it depend on open vs closed...)

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/184#issuecomment-184860236