Home arrow HTML arrow W3C Web Standards

W3C Web Standards

The days of “this site is best viewed in...” are over! We shall no longer be discriminated against for using the browser of our choice. Forget tedious template management, and be prepared to save some dollars on bandwidth! The World Wide Web Consortium have come to agreement on the new Web Standards that will allow us to code and maintain our pages with far less effort, all the while resting assured that everyone can see them as we intended.

Author Info:
By: Justin Cook
Rating: 4 stars4 stars4 stars4 stars4 stars / 42
April 12, 2004
  1. · W3C Web Standards
  2. · An Eagle's-Eye View
  3. · First Component: XHTML
  4. · Attributes
  5. · Second Component: CSS2
  6. · Code Explanation
  7. · Third Component: ECMAScript

print this article

W3C Web Standards
(Page 1 of 7 )

I recall the first time I successfully built a web application that was truly cross-browser functional. It felt great to know that a Mozilla or Opera user would not be penalized with my app. They would see approximately the same visual rendering of the pages, and receive the same DHTML functionality. What did not feel great was the knowledge that literally hours had been wasted just finding ways to 'hack' my own code to hopefully make it work across the board.

This involved everything from creating multiple style sheets, writing JavaScript browser detection functions to determine which style sheet to load, and rewriting other functions to utilize all object and event models properly. Then to ensure proper layout we had tables, then tables nested within those table, then more nested tables with different padding and colors and spacing and alignment and so on and so forth. Of course we can't forget our old favorite, the 1x1 pixel invisible spacer.gif, that we would employ shamelessly to shift around the contents of our pages.

Naturally this dumped all kinds of unnecessary HTML code into our pages, but we could justify it by saying “it's a-OK, the world is all going to broadband”, and we'd throw in a few extra tables for good measure!

But here are just a couple of problems with this rationale. Firstly, what happens when we decide to modify the look of our entire website, even just a little? We want to shift the logo 10 pixels to the right on all 60 pages within our site. If any of you have had the privilege of doing a global search and replace to add in another 10 pixel spacer.gif to 60+ files, you no doubt wished you hadn't.

And then what happens when your site becomes popular, and people (OK, maybe just you) start to visit the site on a portable device? Oh, the pain and humiliation of seeing your wonderfully advanced tabular interface reduced to little more than a complete mess.

But take heart! There is hope! Our friends at the W3C have acknowledged measures of comparison for quantitative or qualitative value, yes, standards. As these relate entirely to the Web, they are aptly named: Web Standards.

blog comments powered by Disqus

- Does HTML5 Need a Main Element?
- Revisiting the HTML5 vs. Native Debate
- HTML5: Not for Phone Apps?
- HTML5 or Native?
- Job Hunting? Freelancer.com Lists This Quart...
- HTML5 in the News
- Report: HTML5 Mobile Performance Lags
- The Top HTML5 Audio Players
- Top HTML5 Video Tutorials
- HTML5: Reasons to Learn and Use It
- More of the Top Tutorials for HTML5 Forms
- MobileAppWizard Releases HTML5 App Builder
- HTML5 Boilerplate: Working with jQuery and M...
- HTML5 Boilerplate Introduction
- New API Platform for HTML5

Watch our Tech Videos 
Dev Articles Forums 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us 
Weekly Newsletter
Developer Updates  
Free Website Content 
Contact Us 
Site Map 
Privacy Policy 

Developer Shed Affiliates


© 2003-2019 by Developer Shed. All rights reserved. DS Cluster - Follow our Sitemap
Popular Web Development Topics
All Web Development Tutorials