You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a NuxtLink, if the href start with a protocol, 'noreferrer noopener' is automatically. While this is great in many case, when you start creating websites links between them, like documentations, you need to know if user come from one of your website.
To do so, the 'noreferrer' need to be removed. While this is possible to pass manually 'noopener' to NuxtLink, it become more complicated when there is new website, many links or even with Nuxt Content.
To solve this, I'm thinking of a white list of URL where only the 'noopener' is set, coming from a key in the Nuxt config file.
Additional information
Would you be willing to help implement this feature?
I also like the idea of a custom link, specially for docs it gives many more options while keeping Nuxt core simple too.
Only the fact that nuxt core adds noreferrer noopenerby default is already involved in the logic...
What got my attention to this issue was first security for external links. I wouldn't add complexity only for the sake of default rel behavior but it got me thinking Nuxt could have an external links policy for security and privacy and it could be joined with route rules. Something to think about.
Describe the feature
Hello,
When using a NuxtLink, if the href start with a protocol, 'noreferrer noopener' is automatically. While this is great in many case, when you start creating websites links between them, like documentations, you need to know if user come from one of your website.
To do so, the 'noreferrer' need to be removed. While this is possible to pass manually 'noopener' to NuxtLink, it become more complicated when there is new website, many links or even with Nuxt Content.
To solve this, I'm thinking of a white list of URL where only the 'noopener' is set, coming from a key in the Nuxt config file.
Additional information
Final checks
The text was updated successfully, but these errors were encountered: