- From: Takayoshi Kochi <notifications@github.com>
- Date: Tue, 17 May 2016 04:49:47 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc:
Received on Tuesday, 17 May 2016 11:50:16 UTC
I have been doing feasibility study and getting feedback from colleagues, and it turned out that having a separate history list for each frame in shadow DOM in Chrome/Blink is harder than I originally thought, and the consistency of browser UI back/forward button for non-shadow `<iframe>` and shadow `<iframe>` navigation made me turn to consider @smaug----'s https://github.com/w3c/webcomponents/issues/184#issuecomment-210474769 again. In the next comment I'll illustrate my current thinking of how browser UI's back/forward buttons and `window.history.go()` work (warning: long). --- 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-219694937
Received on Tuesday, 17 May 2016 11:50:16 UTC