-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
ENH: <a target="_glossary"> #1634
Comments
From Takayuki Shimizukawa on 2014-12-02 07:35:20+00:00 Hum.., in my case, several `.. glossary::`` directives are written in several pages which are not single purpose page for glossary. Because of it, I prefer the current (non target specified) implementation. I propose as an alternative, the behavior can be implemented by using JavaScript. .. [1] http://www.w3.org/TR/2000/NOTE-WCAG10-TECHS-20001106/#gl-interim-accessibility |
From Wes Turner on 2014-12-02 10:37:03+00:00 Thank you for the explanation! I've added this to a few documentation sets, which I suppose either a) interrupts the UX; b) makes tangents (e.g. wikipedia pages) more noticeable:
On further review, I should probably add a checkbox. |
From Wes Turner on 2014-12-02 10:37:21+00:00 Closed. Not a good idea. |
jQuery free version: window.addEventListener('turbolinks:load', function() {
document.querySelectorAll('a.reference.external').forEach(function(link) {
link.target = '_blank';
});
}); |
It would be great if glossary links opened in the same new tab.
The text was updated successfully, but these errors were encountered: