@ac 13:11
hahahahahahahah, lol, if you visit that page, you get 1 single error and something I'm quite proud of.
Nobody has any clue why the w3c removed the target attribute from links, only that now the stance is that you must use javascript to define behaviour, instead of just being pragmatic, that actually, I dont want to add a javascript in order so about 1 links will open in new window.
validation, what most people seem to not realise, is just something to be proud of, if you can get the number of errors to zero, you get brownie points, but you think I am going to fuck about and do javascript JUST TO GET a link to open in a new window?
Are you serious?
REAL developers spend time on REAL problems, not those created by the idiots at the w3c, if you found a REAL error, like, using a <div> inside a <p> tag, then I would agree.
But the best you have got, is using an attribute that actually, I used ON PURPOSE and I know will break the validator and I don't care about it because I have better things to do.
You really think that single link, with a deliberate error, brings down everything I have said?
I bet you are the kinda guy who feels proud at putting those stupid w3c and XHTML logos at the bottom of your page? I did, in 1998, but ten years later, I dont, you know why? Because ultimately, nobody cares, if I had made some serious error, I would agree, instantly. Nowadays it's important your page renders according to the standards, but dont let standards run your life, use your brain, the standards are not so you can turn your brain off, hit a button and get the green ok, standards are for setting your way of developing so that in the future, you can be sure what you wrote is usable and clean and understandable and renders correctly. They are not for making wanking points in online chat over a single error that LOTS OF PEOPLE AGREE WITH.
But you are not going to get far by saying the target attribute is deprecated and therefore we must be using javascript.
There are lots of valid reasons why I want to use target and lots of valid reasons why it shouldnt be deprecated and javascript isnt the best solution, but the "purists", the guys who spent 10 years writing those appauling specs that everyone loves so much, decided to remove it.
Good effort, but unfortunately, no cigar.
Anyone else?