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

FQS links open in new tab #2661

Merged
merged 2 commits into from
Jun 21, 2021
Merged

FQS links open in new tab #2661

merged 2 commits into from
Jun 21, 2021

Conversation

edmofro
Copy link
Member

@edmofro edmofro commented Jun 13, 2021

This is just a suggestion - @enunan do you think the FQS links should open in a new tab or just replace the LESMIS page and stay on the same tab?

@@ -105,7 +105,7 @@ export const TwoColumnPageView = ({ content }) => {
</CardHeader>
<CardBody>
{links.map(({ name, link }) => (
<Link key={name} href={link}>
<Link key={name} href={link} target="_blank" rel="noopener">
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<Link key={name} href={link} target="_blank" rel="noopener">
<Link key={name} href={link} target="_blank">

I don't think we need to add rel any more.
https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types/noopener
Setting target="_blank" on elements now implicitly provides the same rel behavior as setting rel="noopener"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah cool! I guess there's a bit of a risk someone might be using e.g. Chrome from last year, but considering we know the links that are being opened I'm happy to remove it 👍

@edmofro edmofro merged commit fb776e3 into dev Jun 21, 2021
@edmofro edmofro deleted the fqs-links-in-new-page branch June 21, 2021 02:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants