gcaldani wrote:Well, there is a very easy way to workaround that behaviour: right click the link and choose to open to a new tab. So, really don't need to spend time in something the browsers already give you as a choice (at least Firefox and IE).
That's what i do everytime i don't want to lose the actual page and personally I agree being compliant with the standard.
Heh, we better not go too far or we'll be recreating the "discussion" over on the BB boards
Personally, I prefer forum software to continue to support features it *used* to support, and that everyone seems to expect from it. Compliance is nice, but there is no way any browser will drop support for the target property, XHTML or no XHTML
Forum links, seemingly regardless of the forum software being used, always open in new tabs. Just like when you're designing a website, and providing external links - you don't really want the user *leaving* your site in favour of another, be it by accident or otherwise. And yes, I know there are easy shortcuts in browsers to achieve this, but BB has many users and "followers", and for such an obvious piece of functionality to disappear due to compliance that only the developers care about, is quite a surprise. target="_blank" may not be compliant, but it's unlikely that the lack of compliance for that particular property will ever cause an issue in a browser. Evar(tm)
We tried to get them to include it as an Admin option, so it could be the forum owners' decision as to the behaviour (and therefore compliance), and to set the default option to match previous versions of BB - i.e., automatically open in a new tab. They just ignored the requests though
It's most annoying to me, because they have no problems including "invalid" CSS in their stylesheets, to provide the "hacks" neccessary to render properly in multiple browsers. The individual CSS classes/styles are valid, but the way in which their inheritance/cascading is defined, isn't quite valid
Ah well, such is life
hehe
EDIT: Article: Compact JavaScript example of target workaround