Ctrl-clicking on fixed bug links in blog post opens in same tab
When Ctrl-clicking on links, you expect the link to open in another tab. But in snapshot blog posts on http://minecraft.net it still opens in the same tab. Middle-clicking and rightclicking+"Open in new tab" works. Tested in Chrome on Windows 7.
Created Issue:
Ctrl-clicking on fixed bug links in blog post opens in same tab
When Ctrl-clicking on links, you expect the link to open in another window. But in snapshot blog posts on http://minecraft.net it still opens in the same window. Middle-clicking and rightclicking+"Open in new tab" works. Tested in Chrome on Windows 7.
When Ctrl-clicking on links, you expect the link to open in another
window. But in snapshot blog posts on http://minecraft.net it still opens in the samewindow. Middle-clicking and rightclicking+"Open in new tab" works. Tested in Chrome on Windows 7.When Ctrl-clicking on links, you expect the link to open in another tab. But in snapshot blog posts on http://minecraft.net it still opens in the same tab. Middle-clicking and rightclicking+"Open in new tab" works. Tested in Chrome on Windows 7.
Can confirm for Chrome as well
Well, now the weird thing: I just tested it again on two Windows 7 computers with Chrome and it opened in a new tab. But I know for sure that I tested it before on one of these computers and it opened in the same tab. I'll test it again tomorrow on a computer that I had the problem with today.
Ok, tested and it opens in the same tab again. Chrome version 58.0.3029.96. HTML is:
<li>Fixed bug <a href="https://bugs.mojang.com/browse/MC-114930">MC-114930</a> - Narrator not working</li>There's 1 error on the page:
I don't really know what to add else. It seems to be an ordinary link. Ctrl-clicking the other blog posts at the bottom works (new tab). So is there some general thing at the start of the page that changes the behaviour of all links on that page? For example they're also green without having a color tag.
Is this still an issue for you? I can't seem to reproduce anymore.
It seems to work properly now, in Chromium and Firefox.