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

> Possible answer B: the new history state replaces Entry3.
> 
> Entry1: A1
> Entry2: A2 + B1 + C1
> Entry3': A2 + B2 + C1
> Entry4: A2 + B2 + C2


I'm leaning to this. (I got the same idea and then realized that perhaps it was proposed already) 
The replacement happens only when history.back()/go(<0) is explicitly used in shadow browsing contexts. If that doesn't happen, the UI works just the way it works now, since there is the session history transaction list of session history entry trees

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