Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 16 to 17 of 17
Thread: submit form without redirect
01-21-2014, 09:21 PM #16
- Join Date
- Sep 2005
- Sydney, Australia
- Thanked 634 Times in 624 Posts
A lot of the backtracking was done simply to support these web pages that still follow HTML 3.2 (as about 90% of the web does). Tags and attributes done away with in HTML 4 were not reintroduced in HTML 5 because using them is a good idea, they were reintroduced because if they were completely done away with as HTML 4 proposed then it would break 90% of the web. It is also interesting that some tags have been reintroduced just after they became unnecessary (eg. embed which was only ever needed for Netscape 4 but which made it possible to code for both IE6 and other browsers without using conditional comments).
Many of the reintroduced tags in HTML 5 are also only supposed to be used by WYSIWYG web editors that are unable to handle proper styling of the page using CSS. When writing the HTML yourself you can easily do everything you need with the HTML 4 tags and some of the new HTML 5 tags without needing to use any of the reintroduced ones - and get a more flexible page as a result.
Using many of these reintroduced tags and attributes blocks some visitors from being able to use the particular web page.
There are a number of useful tags that have been introduced for the first time in HTML 5 so HTML 5 is an imrovement on HTML 4 in some ways. For example the video and audio tags and most of the new form fields.
One difficulty with HTML 5 is that as it doesn't follow the standards for defining markup languages you have to wonder about how effective it will ever be as a standard. Why should people follow a standard that isn't defined in accordance with the standards for defining that type of standard. As it doesn't follow the SGML markup standard it doesn't have an SGML doctype and so validating becomes meaningless. At least XHTML5 is still defined as XML and XML is defined using SGML so the same issue doesn''t apply to XHTML5.
About the only thing that is certain is that it will finally be possible to use XHTML 1.0 before it becomes possible to use (X)HTML 5 given that HTML 5 is not yet a standard and so current browsers do not fully support it whereas the only browser still in common use that doesn't support XHTML 1.0 is IE8.
01-22-2014, 02:02 AM #17
- Join Date
- Jun 2007
- Thanked 569 Times in 550 Posts
as an aside:
the HTML5 committee felt that xml or especially sgml compliance was not needed or really even desirable. XML is far too strict to be a good document delivery medium. One un-escaped special character and the whole page goes kaboom! A good medium tolerates errors and noise in the signal, and that's exactly what html5 makes even more possible than past versions. By specing a simple grammar and defining how to fail, malformed markup quirks are thing of the past. along with eliminating dependencies on other specifications, this tradeoff makes the web the web more consistent and allows a simplified spelling-out of error routines that would be very complex should XML/SGML compliance enter the picture.