-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After navigating to a new page in an iframe, previous page is not destroyed/frozen #8673
Labels
A-content/dom
Interacting with the DOM from web content
Comments
92 tasks
This happens because the pipelines in iframes are never frozen. |
paulrouget
changed the title
After navigating to a new page, previous page is not destroyed/frozen
After navigating to a new page in an iframe, previous page is not destroyed/frozen
Dec 14, 2015
bors-servo
pushed a commit
that referenced
this issue
Dec 16, 2015
Freeze old pipeline in iframes Fixes #8673 and part of #8674 <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8886) <!-- Reviewable:end -->
bors-servo
pushed a commit
that referenced
this issue
Dec 18, 2015
Freeze old pipeline in iframes Fixes #8673 and part of #8674 <!-- Reviewable:start --> [<img src="https://reviewable.io/review_button.png" height=40 alt="Review on Reviewable"/>](https://reviewable.io/reviews/servo/servo/8886) <!-- Reviewable:end -->
jrmuizel
pushed a commit
to jrmuizel/gecko-cinnabar
that referenced
this issue
Jun 12, 2017
…freeze-pipeline-iframe); r=mbrubeck,jdm Fixes servo/servo#8673 and part of servo/servo#8674 Source-Repo: https://github.com/servo/servo Source-Revision: 2ef972b53bc4ff3783a60bfc45a52beee3065e97
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-comments-removed
that referenced
this issue
Oct 1, 2019
…freeze-pipeline-iframe); r=mbrubeck,jdm Fixes servo/servo#8673 and part of servo/servo#8674 Source-Repo: https://github.com/servo/servo Source-Revision: 2ef972b53bc4ff3783a60bfc45a52beee3065e97 UltraBlame original commit: 715d5bf1ac9d8a947d96f3e71afd0376c7654fab
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified-and-comments-removed
that referenced
this issue
Oct 1, 2019
…freeze-pipeline-iframe); r=mbrubeck,jdm Fixes servo/servo#8673 and part of servo/servo#8674 Source-Repo: https://github.com/servo/servo Source-Revision: 2ef972b53bc4ff3783a60bfc45a52beee3065e97 UltraBlame original commit: 715d5bf1ac9d8a947d96f3e71afd0376c7654fab
gecko-dev-updater
pushed a commit
to marco-c/gecko-dev-wordified
that referenced
this issue
Oct 1, 2019
…freeze-pipeline-iframe); r=mbrubeck,jdm Fixes servo/servo#8673 and part of servo/servo#8674 Source-Repo: https://github.com/servo/servo Source-Revision: 2ef972b53bc4ff3783a60bfc45a52beee3065e97 UltraBlame original commit: 715d5bf1ac9d8a947d96f3e71afd0376c7654fab
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I believe this happens only with documents in iframes.
index.html:
a.html:
b.html:
Running
index.html
, logs are printed in the console. Then navigating tob.html
,a.html
is not displayed anymore, but its JS code is still running.The text was updated successfully, but these errors were encountered: