HTML Elements We Can Kill Off

98 HTML Elements - How Am I Every Going To Memorise Them!

It sounds impossible doesn't it? But it's not (I once learnt a programming language with 1100+ commands!!!). Why don't I make it easier for you to master every HTML element! Why don't we just kill-off half of them! (Now you know why this is called 'The No Bollocks HTML 4 Manual'!)

3 Elements Have Officially Died

Those nice people at W3C have officially killed-off <listing>, <plaintext> and <xmp>. The pre (I) element should be used for all 3 instead.

Cascading Style Sheets Kill-Off 6 HTML Elements

If you don't already know, Cascading Style Sheets (I) were introduced in HTML 4 (The latest version). Don't worry about this yet. They are like learning a whole new language, that has superseded a good bit of the now outdated HTML. The W3C - the folk that invented and update HTML - refer to this outdated HTML as 'Deprecated'. Which means they want them to die a slow death.

These Deprecated Elements Are :

1. <basefont>
2. <center>...</center>
3. <font>...</font>
4. <s>...</s>
5. <strike>...</strike>
6. <u>...</u>

4 Elements Replaced

1. <applet> deprecated in favour of <object>
2. <dir> deprecated in favour of <ul>
3. <isindex> deprecated in favour of <input>
4. <menu> deprecated in favour of <ul>

Think Twice Before Using Frames

The W3C (X) have proved themselves - time and time again - as the leading authority on HTML and the Internet. They know what they're talking about, no one has any doubts about that. They want HTML to be a stable language that doesn't get out of hand. Without them, the Internet would fall to pieces. That's why, even the mighty and arrogant Microsoft listen to them. Frames use what is called 'Netscape's Flawed-Frame Model'. This title blatantly suggests why the W3C have a problem with frames.

Now don't start getting your knickers in a twist. Neither I, nore the W3C are saying you shouldn't use frames. It's just that there are many reasons why you shouldn't. I will be writing an article sometime soon to try and convince you to think twice before using them.

For now though, I will not be including the following 'non-strict' HTML elements in my manual :

1. <frame>
2. <frameset>
3. <iframe>
4. <noframes>

What's The Point ?

What's the point of having an HTML element that does exactly the same thing as another element ?

Nothing of course. But there's two HTML elements that do this :

1. <strong> does exactly the same as <b> (They both make text bold)
2. <em> does exactly the same as <i> (They both make text italic)

Unfortunately for all my praise and admiration for the W3C I fail to appreciate this thing they call 'meaning'. By their reckoning it works like this : If you want to make some text bold (like this) you use <b>; but if you wanted to make text stand out (like this) you use <strong>. Damned if I can see the difference! Can you ?!