I suggest the FIX

<a style="cursor: pointer">

Fixed among other things in remember last "Relate to" options + autofocus + autoselect + MBS-4670 FIX user script.

Sorry but why Won't Fix this inconvenience easy to solve ?

There is no bug and it is not worth anyone's time.

« There is no bug »
Maybe I should have explained the inconveniences :

• It prevents from fast reloading page (address bar, press enter reloads only document and uses cache for all resources).
• It's irritating to find it pasted around instead of the clean URL

« it is not worth anyone's time. »
I can do it, it's worth mine.
The fix is only simple enough for my limited brain power :

<a style="cursor: pointer">Relate to ...</a>

I agree this is annoying and just looks ugly.

The correct fix to this bug is fairly trivial. The Javascript code that opens the pop-up search dialog should return false to cancel navigation. It currently returns true, allowing the browser to navigate to the (non-existant) #relate-to anchor.

I'm going to take a look at doing the JS modification for this change in the next couple days, it's been really annoying me.

+1 for fixing this too.
It has been annoying me for a long time: some userscripts were not running anymore because the URL had changed and was not matching anymore against userscript running URLs.

The issue that I was seeing was that clicking on the button navigated the page, and actually triggered the userscripts twice on the same page - really a bug in the browser, but still

Calvin, I already said it but the no-href style-cursor:pointer is nicer to every cases, reserving the use of this link to only the javascript events and never seeing such a #relate_to copied link anywhere (because of a middle click for instance in Opera that launches the HREF in background tab without triggering the click javascript event). If no href it eventually eliminates all the such problems (I can think of).
It definitively eliminates any bad href copy chances and is the shortest straighforwardest fix.
But anyway if another fix is preferred I guess it will still be better than current.
Thanks for the ticket support BTW.

In IRC chat, jesus2099 said that he'd like to work on this issue.

Thanks Calvin, I want to train myself on some unimportant stuff.
In IRC, Kuno suggested to use a button while not changing the way it is currently displayed (like a link).
As this relate to has a button behaviour rather than a link's.
I agree.

Decision Required
Hi guys this is my first try so please be indulgent.

Do I make the link to button as link solution instead?
There will be more CSS and more JS to insert in MBS.
cf. http://codereview.musicbrainz.org/r/2272/

I did some experimenting earlier this week. It's almost impossible to make a <button> look like a <a> link (consistently in all browsers). So leaving it as <a> is ok.