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

Feature proposal: opener #50

Closed
clelland opened this issue Dec 1, 2016 · 2 comments
Closed

Feature proposal: opener #50

clelland opened this issue Dec 1, 2016 · 2 comments

Comments

@clelland
Copy link
Collaborator

clelland commented Dec 1, 2016

Raised in whatwg/html#2122 (comment), it might be possible to put a noopener policy into FP; rather than insisting that developers annotate every <a> tag. Something like:

{"opener": ["self", "https://friendly-domain.com"]}

would make any links in the current page, except those to the whitelisted domains, behave as if the rel=noopener attribute was added.

This may be an abuse of the whitelist; we've only used it for policy propagation, rather than selectively changing behaviour of parts of the current document, but it might be worth discussing.

(Possibly another interesting thing about making this part of FP is that we could apply it to windows created with window.open as well, which isn't possible with an attribute on <a>.)

@zcorpan
Copy link
Member

zcorpan commented Dec 1, 2016

Please see w3c/webappsec#139

@annevk
Copy link
Member

annevk commented Apr 24, 2019

This is whatwg/html#3740 now.

@annevk annevk closed this as completed Apr 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants