D
dorayme
Tim Streater said:....
Deprecated, obsolete, who cares. Browsers will continue to support these
features until the cows come home. That's all that matters.
Deprecated schmecrecated eh?
Well, it is not quite all that matters generally; but perhaps you
mean it in relation to something in particular. The distinctions
between formal goodness, best practice, browser error correction
have a mildly important status in the scheme of things.
It is probably a good rule of thumb for folk to treat these
distinctions with more caution, the less experienced they are. An
experienced person will more confidently let the formal go in
order to have the advantages of using some particular doctype
(and not bothering to make his or her own).
It is probably not a good idea for inexperienced people to allow
anything that relies on error correction to go ahead in their
work for the simple reason that there is a real slippery slope
here, they do not know which errors all browsers correct
similarly and which do not.
You, being a Mac person, I tell you an anecdote: when I started
using Safari and OS X, I was surprised that it made mince-meat or
simply refused to display things where the HTML or CSS was rather
wrong in various ways. My previous experience had been with more
tolerant browsers, especially Mac IE.