Xhtml why use

Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. Asked 12 years, 6 months ago. Active 1 year, 9 months ago. Viewed 17k times. Improve this question. KdgDev KdgDev Good question; I don't feel like my opinion is worth an answer, but I think it's a waste of time most of the time. Do compliant HTML and call it a day.

This have been asked several times, see for example current top link in the "Related" column WebDevHobo: Please reconsider changing accepted answer, because it is not backed up by any reliable sources, and there are sources refuting it: webdevout. Show 7 more comments. Active Oldest Votes. Improve this answer. Community Bot 1 1 1 silver badge. A nice article and props to you for showing it to us.

MrLister You mean the fact that XHTML actually catches syntax errors and signals them, instead of silently correcting them and leaving latent bugs in your code? Show 2 more comments.

I was going to add this as a comment to one of the other posts, but it grew a little too large. James B James B 7, 4 4 gold badges 31 31 silver badges 40 40 bronze badges. When the vendors of tools and browsers change this situation then perhaps we will be able to start to see some benefits but those who stand to gain the most are not the site developers but the SE vendors. Imagine being able to present rich meaningful info harvested from your sites to a degree where the site itself needs no visit?

What happens to your advertising revenue? Who do you think lives in the ivory towers anyway? The summary of the summary then is that the interoperability benefits of XHTML are threatened by the inadequacies of browser vendors. Separating presentation from markup was a goal that predates XHTML by some time using the strict doctype. And HTML 4 did phase out presentational markup in favor of structural markup. Just because nearly everyone uses HTML 4 Transitional doesn't mean it's a good idea or even recommended by the spec.

Apart from that you don't get true separation as you nearly always have to adapt your markup to your style. And that's not really a good separation of style and content imho. HTML4's 'support' of separation of presentation and markup is sloppy at best. Just because they're not used properly, doesn't mean that the XHTML specification is invalidated in any way.

It's a win-win situation for those wanting to work towards a standards-based web. Your response is very inaccurate. It refers to HTML4 in all aspects related to semantics and presentation. Show 26 more comments. Joey Joey k 80 80 gold badges silver badges bronze badges.

I completely agree. Wholeheartedly agree about XHTML but the development of CSS has been fine until their relatively recent decision to just let the browser vendors work out what the standard is supposed to be. I fundamentally disagree with the argument presented here. I was going to post a comment, but it grew too large, and became an answer below. Developed by those in ivory towers, maybe I guess all the upvotes to that posting show two things: 1.

Show 1 more comment. Stylesheets were introduced in HTML4. Presentational elements were deprecated in HTML4. This alone is usually more work than parsing of the document itself.

HTML parsers almost always "cheat" and use hardcoded entities and element information. XHTML parsers in browsers cheat too. Draconian XML rules require checking if every character is properly encoded. Kornel Kornel Add a comment. There is no simple answer and the benefits you will gain are tied to the context and the use of the language.

Switching from HTML 4. It seems to be a reasonnable way of improving one's competences without too much work. W3C liability , trademark , document use and software licensing rules apply. Cloud Computing.

Data Science. Angular 7. Machine Learning. Data Structures. Operating System. Computer Network. Compiler Design. Computer Organization. Discrete Mathematics. Also, you can insert image and a link to another page in your code. Both fields are best at their place.

They create designs to give the look to a web. Whereas the developer builds the backend of the web. A Developer needs to work on the functionality of the website and designer needs to give it an interactive and user-friendly design.

Don't have an account? Sign Up. Already have an account? HTML 5 Tutorials. Related Tutorials jQuery. HTML 5. View More. Aman Goel. Table of Contents. Markup Languages: What Are They? Front-End Development Web Development html5 html xhtml. Leave a comment. Submit Cancel. Toby Wood. Robin Strickland. Spencer Spencer.

Douglas Woods. Eliot Trevino. Jordan Little. Mayson Hampton. Alfred Daniels. Frederick Harrison.