I'm a developer who likes testing first, iterative processes, and refactoring, and I care about quality. I speak both C and Ruby with some facility, and enjoy both, which confuses some people.
Thanks for keeping links working the way they were intended. Opening in a new tab/window is easily accomplished with a middle click, but forcing something to open in the same tab/window when a site has decided to force things to open in new tabs/windows is not so straightforward.
There are occasions where opening a link in a new tab/window is a good idea but, when in doubt, leave it out. Give the user choice based on standard approaches.
I'm a developer who likes testing first, iterative processes, and refactoring, and I care about quality. I speak both C and Ruby with some facility, and enjoy both, which confuses some people.
I'm just saying that links that work the default way -- opening in the same browser tab/window normally, but in a new tab/window when someone middle-clicks -- are usually a good idea. It seems that is how your website works, and I think that's a good thing, even if Twan Mulder thinks you should change it.
Thanks for keeping links working the way they were intended. Opening in a new tab/window is easily accomplished with a middle click, but forcing something to open in the same tab/window when a site has decided to force things to open in new tabs/windows is not so straightforward.
There are occasions where opening a link in a new tab/window is a good idea but, when in doubt, leave it out. Give the user choice based on standard approaches.
Sorry, but I didn’t understand your point of view... Can you explain it better?
I'm just saying that links that work the default way -- opening in the same browser tab/window normally, but in a new tab/window when someone middle-clicks -- are usually a good idea. It seems that is how your website works, and I think that's a good thing, even if Twan Mulder thinks you should change it.
Thanks. I decided to follow your advice: now the links open in a new tab 😊