Skip to content
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

Event handlers on closed pipelines can trigger panics #17344

Open
jdm opened this issue Jun 15, 2017 · 1 comment
Open

Event handlers on closed pipelines can trigger panics #17344

jdm opened this issue Jun 15, 2017 · 1 comment

Comments

@jdm
Copy link
Member

@jdm jdm commented Jun 15, 2017

This turns out to be a generalization of #16057 which I realized when thinking about whether #17323 was testable.

<iframe src="about:blank"></iframe>
<script>
  var i = document.querySelector('iframe');
  i.onload = function() {
    var e = i.contentDocument.body;
    e.onclick = function() { e.clientLeft };
    i.remove();
    setTimeout(function() { e.click() }, 0);
  }
</script>
@jdm
Copy link
Member Author

@jdm jdm commented Jun 15, 2017

When I run this test in Firefox, adding a console.log to the handler demonstrates that Firefox happily invokes the event handler. We may need to change how we implement Window::clear_js_runtime and the DOM APIs that query layout if they need to be able to work after a document no longer exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.