-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add external-link-icon handling #59
Comments
What are your thoughts on this @tardinha - implement via JS and/or via a shortcode in the editor field ? Custom templates can implement as required, and any global implementation would have to check that the external link icon is not already present. |
Can we automate it like we do already with files? In the old days, we'd do it purely in CSS... |
The implementation examples is like this: <a class="js-link" href="https://digital.nsw.gov.au">
<span>My Link</span><span class="material-icons nsw-material-icons" title="(opens in new window)">open_in_new</span>
</a> If we had a link like the below, some JS could be used to check if it is an external link and add the relevant HTML... maybe ignore if it already has the class <a href="https://digital.nsw.gov.au">My Link</a> Separate to the implementation detail is - does having an external link icon improve anything ? |
I like the external icon, but not opening in a new tab. I guess everything else is JS driven... i'd prefer a non-JS solution. |
It looks like the nswds ExternalLink component adds the _blank target for any element that has a class "js-link" but the implementation/template adds the chosen icon (open_in_new_window in the docs). const link = document.querySelectorAll('.js-link')
// ....
if (link) {
link.forEach((element) => {
new ExternalLink(element).init()
})
} For the editor field, maybe there is already a shortcode option for adding an external icon when the link is to a different domain, and the target is only determined by the person editing. |
Reference: https://digitalnsw.github.io/nsw-design-system/components/link/index.html
The text was updated successfully, but these errors were encountered: