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

Let me try to move forward - we seem to got stuck, no perfect idea to solve all the constraints and concerns so far.

As we illustrated in https://github.com/w3c/webcomponents/issues/184#issuecomment-219905487 and https://github.com/w3c/webcomponents/issues/184#issuecomment-219928308, if we had separated joint session history to document and shadow iframes, it is expected that there would be inevitable browser back/forward button behavior inconsistency against user expectation.

If anyone cannot come up with a way to make it compatible with how back/forward button behaves on current browsers, we cannot mandate the separate list idea in V1.

As in @annevk's https://github.com/w3c/webcomponents/issues/184#issuecomment-184860236
> 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.

there's much possibility that current behavior is anticipated.

Any wisdom?
@rniwa @smaug---- @annevk @travisleithead 

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