User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0E) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729; .NET4.0E) When selecting "open in a new tab" for a javascript link, Firefox goes ahead and opens a new tab, which then fails to do anything useful. Most of the time the script is just "void()" anyway. While making "open in new tab" work for all links would be really rather neat, the current behaviour could be improved as an interim stop-gap measure. Specifically, when selecting this action for a javascript link, the browser should just process it as if it was clicked normally, instead of creating a new tab. Motivation: go to a javascript-heavy website (every other one these days), middle-click a few links "to see later", close the original page, and face a whole bunch of blank tabs. Not nice at all. Reproducible: Always Steps to Reproduce: See Details. Actual Results: Javascript links open in a new tab and fail to operate properly. Expected Results: (the trickier alternative most certainly covered in a separate bug) Clone the current page and process the click there. (the stop-gap approach to the very annoying current behaviour) Just pretend the user clicked the link normally.

Reporter, can you still reproduce using a current version? If no, please set status to RESOLVED and resolution to WORKSFORME. If yes, please provide updated information.

Yes, it still happens: - open this example http://jsfiddle.net/N73VS/2/ - click Link 1 and Link 2; observe some divs changing - middle-click one of those links; observe a useless "javascript:;" tab open. This behaviour means that I don't know whether my middle click had the desired effect until I check out the newly created tab. If at least the new tab didn't appear at all and the middle click was processed as a click, I would at least have some indication that the link is not new-tab-friendly.