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

@smaug---- is the concern shadow-dom specific?

I may not be understanding the case you quoted. In my understanding the injected Google Ads script mistakenly ran `history.go(-1)` which expected to navigate some `<iframe>` to go back to its history, but the history was empty and the main document went back, right?
This can easily happen if there are more than one injected `<iframe>`s and script tries to go back and forth independently for each `<iframe>`.

That's a reasonable concern but it should be addressed at *nested browsing context* and history API's behavior or *joint session history*, not at the level of shadow tree boundary.


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

Received on Friday, 15 April 2016 03:24:18 UTC