-
Notifications
You must be signed in to change notification settings - Fork 29
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
[Spec] Window.close should do nothing #26
Labels
specification
Additions to specifications
Comments
Per https://html.spec.whatwg.org/#dom-window-close, the spec currently operates in terms of top-level traversables (aka "outermost" or "primary" frames), so spec-wise we're all set here actually. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
window.close() on a fenced frame shouldn't start the window closing steps.
Chromium had a bug where this was observable via window.closed() but it should likely do nothing an exit early before starting the closing steps.
See https://chromium-review.googlesource.com/c/chromium/src/+/3607497 for context (and a WPT test)
The text was updated successfully, but these errors were encountered: