Why isn't XHTML2 backwards compatible?
Answer / guest
It is, but in a different way to how previous versions of
HTML were backwards compatible.
Because earlier versions of HTML were special-purpose
languages, it was necessary to ensure a level of backwards
compatibility with new versions so that new documents would
still be usable in older browsers. For instance, this is why
the <meta> element has its content in an attribute rather
than in the content of the element, since it would have
shown up in older browsers.
However, thanks to XML and stylesheets, such strict
element-wise backwards compatibility is no longer necessary,
since an XML-based browser, of which at the time of writing
means more than 95% of browsers in use, can process new
markup languages without having to be updated. Much of XHTML
2 works already in existing browsers, browsers that are not
pre-programmed to accept XHTML2. Much works, but not all:
when forms and tables were added to HTML, people had to wait
for new version of browsers; similarly some parts of XHTML
2, such as XForms and XML Events, still require user agents
that understand that functionality.
| Is This Answer Correct ? | 1 Yes | 0 No |
What are chainstays?
What are the two types of html5 web storage?
What is wrong with my <meta> tags?
What are tags and how do you use them?
What is the difference between html and xhtml?
What is p tag?
What are empty elements?
How do you make frames?
What is scss in html?
What is div short for?
How many types of html tag are there?
What happens if doctype is not specified?