It is helpful for website logins to autofill usernames and passwords on HTML inputs, but can be a pain in the butt when you work with password change/reset forms or forms with credit card number fields. In these instances, you don’t want numbers to automatically fill in (or be remembered by a browser). Learn how to stop it.

Like most web developers who publish articles, I always preach about standards and best practices (which, incidentally, makes me wonder why we don’t see more loud-mouthed naysayers who try to get recognition by writing about how all that is a big joke.) This article will be no different, except this time no one can argue about whether it makes a real difference. Today, I will be talking about progressive enhancement. Enhance it!

Max J Mammel
Guest Author: Max Mammel
Max Mammel is an Indianapolis-based Technical Lead of a web application development team with a global Fortune 500 firm. Max is an expert in design patterns, system architecture, and object-oriented programming and brings many years of Java know-how to SolidlyStated.com

I suspect that there are nearly as many solutions to the problem of email address validation as there are projects that require them. I’ve seen a fair amount of them myself over the years, they range from simply checking for the presence of an @ in a string to extremely complex and often flawed sub-routines designed for the task. Get a proper script

Welcome to another article on Building Better Web Pages. This article series comprehensively covers building an HTML document: easily learned, but rarely perfected.

Today’s article covers Doctype declarations in regards to XHTML and HTML.This is one of the most intriguing markup debates out there. I personally waffled back and forth between the two.

Solid Statement: Don’t be a whiny prima donna about this issue. The XHTML Doctype helps you develop good coding habits. While HTML 4.01 has its set of standards, it allows for ‘sloppy’ code that doesn’t fly in any other language or platform.

See the pitfalls to both.

Welcome to another article on Building Better Web Pages. This article series comprehensively covers building an HTML document: easily learned, but rarely perfected.

Today’s article covers Strict versus Transitional Doctype declarations. This is an extended discussion regarding the article about Doctype declarations. I always suggest XHTML Doctypes. There is some interesting debate over the HTML vs XHTML, but it is becoming less relevant as the web continues to mature. How Does Strict Benefit Me?

Welcome to another article on Building Better Web Pages. This article series comprehensively covers building an HTML document: easily learned, but rarely perfected.

Today’s article covers Doctype declarations. While there is a wealth of information on the internet already about Doctypes, I have always clicked away without really understanding what was really going on. Besides, we can’t completely cover “Building Better Web Pages” without it. The most basic questions are “Why do I need a Doctype?” or “Which Doctype should I use?” You might figure this would be easy to explain. I think can be, but I just never see it solidly stated.

Welcome to another article on Building Better Web Pages. This article series comprehensively covers building an HTML document: easily learned, but rarely perfected.

Today’s article covers W3C Validation and Nested Tags. Some designers swear by the W3C standards like a bible, which they like to thump. The opposition likes to call them out and make a general mockery of things. Either way, HTML validation helps you uncover errors that may or not be affecting the rendering of your page, its search engine ranking, or both. Discover Why.