Last modified: 2014-02-12 23:53:04 UTC
Current behavior on Special:Nearby is to load the target page no matter if you right- or left-click on the target. This affects both mobile and desktop browsers. Use-cases would be if you wanted to open in a new tab while keeping the nearby list open.
I just tried this on mobile and it works fine https://en.m.wikipedia.org/wiki/Special:Nearby What browser are you using? Are you using beta or stable mode of the site?
I believe he's using <https://en.wikipedia.org/wiki/Special:Nearby>.
Both URLs do the same on mobile (using stock android browser and latest Chrome which I believe just skins the stock app) and desktop Chrome and FF22. The right-click works, but loads target in background when it shouldn't.
OK this seems to be on a desktop browser but does not effect a mobile browser. Thanks for clarifying. I believe this is due to the preview mode in the beta of this site.
Jon, this is *indeed* on a mobile browser as well. I have a Galaxy s4 running android version 4.2.2.
Change 78348 had a related patch set uploaded by Jdlrobson: Bug 51647: Allow right clicking on nearby https://gerrit.wikimedia.org/r/78348
Change 78348 merged by jenkins-bot: Bug 51647: Allow right clicking on nearby https://gerrit.wikimedia.org/r/78348
*** Bug 53092 has been marked as a duplicate of this bug. ***
What about middle click and CTRL+click?
What exactly is your experience when you middle click or ctrl click? These seem to work fine for me now.. are you on mobile or desktop? If on mobile which version of the site are you running - beta, alpha or stable?
I'm using Google Chrome 29.0.1547.57 under Linux Mint, and when I try to open a link in a new tab using the middle button or CTRL+click, I get the target page loaded both in the current tab (Special:Nearby) and in a new tab. I don't want it to change the current page. I tested on English Wikipedia: https://en.wikipedia.org/wiki/Special:Nearby
Weird it seems to only effect the desktop site and on middle click - not entirely sure why. I've opened a new bug to report this (bug 53188).