Remove obsolete items from future browsers?

Question

What are the disadvantages of using obsolete elements if I'm not interested in validation and I use a DTD that supports them? Deprecated items will not be displayed by future browsers?

Some WYSIWYG online editors (which we use in the CMS) still produce output in outdated elements. Should I spend time changing output for a client?

alt text http://easycaptures.com/fs/uploaded/241/3445655293.jpg

Should obsolete items be avoided at all costs?

Currently, all major browsers show all obsolete elements.

I just wanted to know the disadvantages of using outdated elements to provide to a non-technical client, even if everyone works today in all browsers.

Update:

you can come up with guide 1.3, make sure that information and structure can be separated from the presentation using font and alignment of elements, if you like. Yes that's right. You can use an element that was deprecated in HTML 4.01 nine years ago, which links the presentation of your page to the page structure and content - theres no criterion for success telling you not to use obsolete functions, and you can still pass all success criteria for states to “ensure so that information and structure can be separated from the presentation. " And is this a step forward?

I found this in this article http://accessites.org/site/2006/06/the-wcag-20-what-a-whopper/

Answer 1

Firstly, obsolete items are usually not the best items to use. They are usually out of date for some reason, as there are better ways to do this.

Secondly, they could go away in future browsers. (Will they be a difficult question.)

For these reasons, you should always avoid legacy features. You should not avoid it at all costs, because outdated functionality is almost never the best way to do something.

Is it worth it to change an existing product, this is another question. In most cases, websites need to be revised for other reasons later, and this may include removing obsolete items. Many of them will be removed from the Internet (for various reasons) long before any browser that does not support them will gain popularity.

However, you are talking about an instrument, and that is different. The tool should be more rigorous than the final product, since it affects not only today's work, but also work in the uncertain future, thereby increasing the chances of problems. I would say that the tool needs to be changed.

Answer 2

Future browsers may not support them, and you should always follow the specification. If you're used to deviating from trivial HTML, your future as a professional programmer will be dull.

If you use an editor that still uses obsolete elements, you should replace them. Fortunately, it can be as simple as the find / replace command.

Answer 3

Usually there is a reason for obsolescence of things and most often another way to do the same that is not outdated.

Answer 4

Against?

well ... they are out of date .