Tag: XHTML 1.0

Working draft of HTML5

Are you ready for next gen HTML5 with DOM interface?

I am amazed even removing iframe from XHTML 1.0 “strict mode” they have included it once again in HTML5 with better control.

For the lovers of Web Forms 2.0:

Design a form that uses autocompletion (intellisense for me) like we do using AJAX (not up to that) could work in simple HTML elements.


<input type="url" name="location" list="urls"/>
<datalist id="urls">
<option label="MIME: Format of Internet Message Bodies" value="http://www.ietf.org/rfc/rfc2045">
</option><option label="HTML 4.01 Specification" value="http://www.w3.org/TR/html4/">
</option><option label="Form Controls" value="http://www.w3.org/TR/xforms/slice8.html#ui-commonelems-hint">
</option><option label="Scalable Vector Graphics (SVG) 1.1 Specification" value="http://www.w3.org/TR/SVG/">
</option><option label="Feature Sets - SVG 1.1 - 20030114" value="http://www.w3.org/TR/SVG/feature.html">
</option><option label="The Single UNIX Specification, Version 3" value="http://www.unix-systems.org/version3/">

…if user type ‘www.w3’, and UA* had found that it’s already had visited http://www.w3.org/Consortium/#membership and http://www.w3.org/TR/XForms/ in the recent.

There are many more, surly you will love it as I am.

What are Web Standards?

The term web standards can mean different things to different people. For some, it is ‘table-free sites’, for others it is ‘using valid code’. However, web standards are much broader than that. A site built to web standards should adhere to standards (HTML, XHTML, XML, CSS, XSLT, DOM, MathML, SVG etc.) and pursue best practices (valid code, accessible code, semantically correct code, user-friendly URLs etc.).

In other words, a site built to web standards should ideally be lean, clean, CSS-based, accessible, usable and search engine friendly. Read More