Page MenuHomePhabricator

Evaluate `target="_blank"` usage on Style Guide pages
Closed, DeclinedPublic

Description

We've currently using target="_blank" on some external links. Should we provide it consistently within our contents, adding [[ https://mathiasbynens.github.io/rel-noopener/ | rel="noopener" ]] for security reasons (see also T188698) or leave it completely up to the user?

Update: This article is also pointing out [[ https://blog.dareboost.com/en/2017/03/target-blank-links-rel-noopener-performance-security/ | performance issues when setting target="_blank" ]].

Proposed outcome: We should probably not set it. Thoughts?

Event Timeline

Volker_E triaged this task as Lowest priority.Mar 15 2018, 9:56 PM
Volker_E updated the task description. (Show Details)

The performance concerns (resource contention due to same thread used) seem very slight in a normal use case, imo. I dont think we should worry about that unless we can actively measure the difference.

Unless absolutely necessary I'd not add target="_blank" and leave it to the user.

We should probably not set it. Thoughts?

There's an additional use case now, the linking of binary files from the repo's HTML files, like Sketch or Adobe Illustrator files. `target="_blank" is helpful for browser downloads.

Don't see this happening now, there are certain links where we rely on target="_blank" and it actually seems more helpful for user causes than hurtful. Can pick this up again, if there are new insights on how to better handle site-external links.