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
First and foremost this was a great little addition to the nav. However ran into a few issues:
Accessibility: Because these are just spans, screen readers and other form of link detection have no idea the item is a link object to navigate to another page. This can also impact any SEO from these link outs [They are in a nav html block, so some do at least parse it, but not all)
Because these are not links and JS open. There is no way for a user to open these in a new tab, the normal methods of CTRL+Click, Middle mouse button, or right click and open in new tab, do not work due to this not using links. (tho all three options can be supported in a JS click event)
It would be great if we can choose how the links function (EG default opening in a new tab instead of having the users leave the forums for external links)
The text was updated successfully, but these errors were encountered:
alxndr
added a commit
to alxndr/discourse-dropdown-header
that referenced
this issue
May 28, 2024
First and foremost this was a great little addition to the nav. However ran into a few issues:
Accessibility: Because these are just spans, screen readers and other form of link detection have no idea the item is a link object to navigate to another page. This can also impact any SEO from these link outs [They are in a nav html block, so some do at least parse it, but not all)
Because these are not links and JS open. There is no way for a user to open these in a new tab, the normal methods of CTRL+Click, Middle mouse button, or right click and open in new tab, do not work due to this not using links. (tho all three options can be supported in a JS click event)
It would be great if we can choose how the links function (EG default opening in a new tab instead of having the users leave the forums for external links)
The text was updated successfully, but these errors were encountered: