open link in new page
AliMD opened this issue · 227 comments
how can add target="_blank" to markdown links [test](http://test.com) in github?!
It seems unlikely that this will ever become a feature of markdown or gfm.
That said, you can use standard HTML to add a link that targets a new window/tab:
<a href="http://example.com" target="_blank">http://example.com</a>
Hmm, your example link rendered as:
<a href="http://example.com" target="_blank"></a>
<a href="http://example.com">http://example.com</a>So clicking the visible link doesn't actually open the URL in a new window. 😞
However, it does work properly if the body of the link isn't a full URL:
example
However, it does work properly if the body of the link isn't a full URL:
example
Ahh, interesting. I guess that makes sense.
Would adapting the “Kramdown extension” to use [link{options}](http://kramdown.gettalong.org/syntax.html) be an option?
@paulmenzel now working in github
Same @trliner, from what I've read, multiple people have had to revert that fix because github flavor markdown doesn't support it.
The issue is still open since 23 Nov 2012
Looks like it is not working...
<a href="http://stackoverflow.com" target="_blank">Go</a>
Same problem with my README. The raw Markdown has the HTML but it's being scrubbed off somehow when it's rendered.
I wonder how come this simple feature issue is open since 2012 (4+ years seriously???).
And before finding out this issue being reported here, I was giving syntax check again and again to kramdown ...
Wish Github starts supporting this feature
So its now August and I am gonna keep talking about this. Why is there no solution to this ?
@github
Same here, even entering plain HTML with target='_blank' set does not work.
Github doesn't implement new custom extensions to Markdown format and looks towards CommonMark. I think that commonmark/commonmark-spec#105 should be approved and merged into CommonMark specification first, then Github would implement this common specification in GFM.
Wow, it blows my mind that there isn't a simple way to do this. Who doesn't find it annoying when tabs open in the same window? That should not even be the default behavior. Worse, it is apparently something that can't even be remedied right now. Sad.
This is really sad
Also have a need for this.
Same here
Ditto
+1
Bump.
+1
holy heck, guys, github leaves dis issue for SO LONG! whoa!
plus, I have the same problem
+1
+1
+1
+1
+1
+1
+1
+1
+1
+1
+1
still waiting on this....
why? this is as old as the whole www.....
Why is implementing a target such a problem?
+1
+1
+1
+1
+1
+1
+1
+1
+1
+1
{:+1="_one_more_year"}
+1
+1
+1
+1
+1... lol.
+1
+1
+1
+1
+1
+1
+1
+1
+1
+1
+1
Users, please stop write +1. Use reactions (Emojis) at first post.
Collaborators, please lock this conversation.
+1
Is this being seriously considered? Leaving a project page is bad user experience in most cases and just involves going back and forth. At least having the option would be nice.
+1
+1
+1
+1
+1
+1 - I'm surprised opening links in a new window isn't already a built-in feature, this is a basic function that should be implemented
+1
+1
+1
+1
+1 - I'm surprised opening links in a new window isn't already a built-in feature, this is a basic function that should be implemented
How many +1 do we need to implement this feature?
Looks like @AlexWayfer took their sweet time to downvote all the comments. Impressive to be honest.
@starikcetin Only "+1" unhelpful comments. I've asked to not write this… rubbish, and rate the first comment (issue starting).
I don't want to someone leaves my readme/wiki page back and forth while navigating. It's actually very sad to see no one gave a fuck on this issue. 👎
I don't want to someone leaves my readme/wiki page back and forth while navigating.
Use HTML <a> tag.
Use HTML
<a>tag.
You mean this?
<a href="https://www.google.com/" target="_blank">google.com</a>
Not working.
+1
++1
2 plus signs to check if AlexWayfer has a bot in the background or is srsly doing this manually ^^
as in many cases, the devs doesnt mind our +1 or upvotes.
if they wanted to do that, they could have done in 2012, in several days after opening this topic, because it doesn't need much thinking, that this feature will be needed by many people.
just, they say NO.
It will be a bad more sign and unprofessionalism of devs, if they fixed this problem at this moment (after 6 years of raising the issue). so, i suppose this is "won't fix".
2 plus signs to check if AlexWayfer has a bot in the background or is srsly doing this manually ^^
I don't want to waste time for a bot.
I'm subscribed to this issue (via button at the right menu), and I'm receiving many useless +1 in my email, and I don't want to receive them. I've asked about this, but people don't want to hear others.
I was wrong with <a> tag suggestion, I didn't think that GitHub cuts attributes from tags. My bad.
+1
@Harti, I want to get updates of this issue. +1 is not update.
Just set yourself a reminder then, every year. Put the link in the reminder‘s notes, or bookmark the issue.
Chances are this will still be open and unresolved every time you view it.
But getting salty because other people are using this platform to nag the developers to tackle this actually important feature, and are disturbing your inbox peace, is ridiculously childish and entitled.
Just set yourself a reminder then, every year. Put the link in the reminder‘s notes, or bookmark the issue.
Just don't write +1. It's pointless.
Instead of every interested person like me changing subscription to issue to a reminder, I'm trying to change the whole situation, make public issue discussions more informative. One situation, one rule, instead of many moves of many people.
But getting salty
I'm just trying to make this place better, without aggression.
because other people are using this platform to nag the developers to tackle this actually important feature
No, +1 doesn't nag the developers. If they will want to do something from issues of this projects — they'll use sorting by 👍, I'm pretty sure. Look, this issue is already the first: https://github.com/mojombo/github-flavored-markdown/issues?q=is%3Aissue+is%3Aopen+sort%3Areactions-%2B1-desc
And +1 comments don't help for this sorting, nor don't nag the developers, nor don't give some useful information for all 80 participants of this issue.
So, please, use 👍 button at the issue-starting comment, subscribe if you want to watch for this issue, and be free. +1 comments are obsolete, before emotions buttons feature. Don't litter emails of dozens of people with absolute trash like +1 comments.
Just unsubscribe from it. You're creating more spam, thus making me truly wonder if alleviating spam is truly your desire rather than just a simple pet peeve that people aren't using the system the way you desire it to be used.
Just unsubscribe from it.
No.
You're creating more spam
No.
No.
Yes.
No.
Yes.
Yes.
I'll not.
Yes.
Just count before you claim in order not to be a liar.
I just wanted to prove that you had no desire to clean up spam. Thank you for making that way easier than I anticipated. Now we know we can just ignore your nonsense and have a clear conscious of doing so.
+1
GITHUB Y U NO
Clippy, help?