Comments on: Opera: Just 4.13% of Web’s Code is Valid

By: yman

yman — Sat, 08 Nov 2008 10:06:45 +0000

Tabbed browsing, Quick Find, fraud protection, saved sessions, Speed Dial, notes and the trash make from Opera Browser, a browser more better than it was. Significant speed allow you to spend more time online. I installed it, it works very well and i got it from here: Opera Browser

By: Srirangan

Srirangan — Fri, 24 Oct 2008 08:50:37 +0000

Except for us iCAB users. 8^)

Yepp.. All 8 of you.. :P :)

By: Anonymous

Anonymous — Fri, 24 Oct 2008 07:41:20 +0000

I use iCAB as a browser. It is relative to this thread because iCAB has a little smiley in the bottom row that scowls whenever it shows a page which does not validate. A click will pop up a list of all the errors. Is that neat or what? Handy too!

Now I realize that iCAB is a Macintosh only product and that Kevin never recognizes it in his epistles. However it is a very competent little browser and wll parse just about everything. It worked on the
Acid Test from the start. Very laudable from a shop which is essentially a one man operation.

Why should you validate? Because it makes your client appear to be lazy and sloppy if you do not. Of course who’s going to know? No one is going to read your source code.

Except for us iCAB users. 8^)

By: SimonPhoto

SimonPhoto — Thu, 23 Oct 2008 12:22:34 +0000

“..It doesn’t matter if your page isn’t 100% XHTML 1.0 Strict valid..”

Oh, yes, it does. XHTML, if served properly, will give nothing but an error if there is a single error in the markup. XHTML is an XML-based language, and therefore must be well-formed. HTML is SGML-based, and gives you much more leeway.

That said, most of my pages don’t validate via the W3C. I follow the standards though, to the point where it is practical. In many cases, you have a choice: meeting your client’s expectations, providing unfettered access to all users, and following the standards. Choose two.

Sorry guys, but strictly following standards is not a must-have. Its a nice-to-have.

By: topdown

topdown — Wed, 22 Oct 2008 21:43:32 +0000

What it comes down to is if your not going to use the tools set out for you, and check your work, then it’s your own fault when a customer complains about display issues in a particular browser. IE is no exception, and your code should not need hacks, you should just understand the needed CSS for the particular browser to display the page properly.

If you are going to call your self a developer and develop web pages, you need to know your field and the software the consumers will use to view it.

There is simply no reason for bad or non valid code !

By: Shadow Caster

Shadow Caster — Wed, 22 Oct 2008 20:35:11 +0000

I think perfectionists are the sort of people who really stress on validation of all their pages. In terms of how a search engine looks at it, it doesn’t matter if your page isn’t 100% XHTML 1.0 Strict valid – it won’t mark it down so SEO is unaffected. One of the few reasons why they should make it valid is so that it looks and behaves correctly in the 4 major browsers, but quite often it doesn’t even if it is valid and we have to employ little tweaks.

By: Antz

Antz — Tue, 21 Oct 2008 20:37:14 +0000

What a thing to wish for Alex, browsers ~~supporting~~ enforcing standards! It would certainly be valuable to assist certain developers who have not yet learned a correct way to code, and could possibly be our opportunity to ditch non-compliant browsers such as IE6.

True enough, there will need to be an ability for browser manufacturers to register their proprietary commands to avoid such errors.

By: SonFishDesign.com

SonFishDesign.com — Tue, 21 Oct 2008 18:44:54 +0000

This site has 5 errors in the html but validates css 2.1

By: SonFishDesign.com

SonFishDesign.com — Tue, 21 Oct 2008 18:34:24 +0000

My last client page leans heavily on CSS. The whole page is complient except for the -moz-box-sizing hack. Enough said.

By: Srirangan

Srirangan — Tue, 21 Oct 2008 18:12:50 +0000

I think the developers need to all agree on one standard and stop with all the proprietory browsers

Let’s stop pretending that developers actually have a choice here. Standards are all good, but in the end usability counts. Which usually means different hacks for different browsers. :-/