Well, Scott, let me remind you that "deprecated" is a word which indicates a
kind of warning, if you will, that something is not going to last. The word
"transitional" indicates that something is being supported during a
transition phase from one set of standards to another, and a transitional
phase lasts only as long as the transition.
Yes, browsers may support this tag (and other deprected tags and elements)
for some years to come, but eventually they will not, and in the meantime,
being deprecated, it (and other deprecated tags) may not work as well over
time, as they come into (possible) conflict with emerging standards.
Bearing this in mind, and being a developer who doesn't want to overburden
himself in the future, while I am not going back over everything I've
created to date and updating it, neither do I want to have to do so all at
one painful whack in the future. So, my personal strategy is to work with
the new standards when I am doing new work, and to avoid deprecated
standards as much as possible. Older work I leave as is, unless I have to do
some maintenance or other upgrade type work on it, in which case I may, if
convenient, do a bit of standards upgrading as well.
Of course, this is not something I am touting as "the right way" or "the
only way" to do things, but I hope you may find it food for thought.
--
HTH,
Kevin Spencer
Microsoft MVP
..Net Developer
If you push something hard enough,
it will fall over.
- Fudd's First Law of Opposition
