I'm happy to debate this with you but it would help if you had something constructive to say.

You just told everyone in this thread that you're better than them, I think that kind of knocks debate on the head.

Yep, I've taken a side: adhering to standards is better than not.

Isn't that how you start a debate?

We all know the benefits of standards-based design. People doing this stuff seriously (as in, for a living) that don't adhere to standards are, in my opinion, less professional, because they're not keeping up with the rest of the industry.

Are you disagreeing with me? Do you adhere to standards yourself? If not, why don't you? Is it a time issue? Do you not agree with the perceived benefits of standards? Is this perhaps not your main job, in which case, the time to learn this stuff isn't worth it?

Come on, discuss!

I've already stated my opinion Paul, and I'm afraid I don't debate with people with superiority complexes. When you need a hand dismounting, gimme a shout.

adam

Nothing like a difference of opinion to spice up a Sunday eh

__________________
Hosting & Domains|Plesk Vps Hosting|Geek / Cool Stuff|Films.ie|Cool Sites|Monetisation Tips|Movie Chat


Energise your forum! Click here for info

to answer frankp (http://forum.search.ie/t45-do-you-ma...compliant.html)

ok admitedly, I should not have said 'not being asked', and using that as a valid reason not to design to web standards.

however I would like some people to answer the following


1. why should i code for mozilla/firefox when the majority of end users still use IE. If I code my css for Mozilla/Firefox I know that I will have to make corrections in IE and dare I say it, make a few IE specific hacks

2. Would u consider a site that is viewable in multiple browsers - somewhat standards compliant? Even though not all browsers (across different platforms) confirm to what is considered "standard"?

3. If we are encouraged to use "web standards", why is there is so much work involved in getting right across the board when developing?

Whilst I am aware of web standards, etc, blah, blah - it doesnt necessarily mean I will use them. I use tables on some sites, and not strictly limited to tabular data (as recommended). I just know from experience that, across the board - tables are more then likely able to display a page how I need to.

That is not to say there is no room for css/div in my current and past development but I wont be relying solely on them

Firefox is becoming more prevelant so will start to make up more of your client base. IE7 will be much more standards compliant then IE6.
The corrections you have to make to IE is bacause IE is wrong.
coding to standards also means that you will not have to go back and change things at a later date.

That has been the root of the problem for years, back during the browser wars in the mid 90's microsoft and netscape kept adding their own proprietary functionality and did not follow any of the W3C's recommended standards. When Microsoft "won" they stopped developing IE and hence how far IE is now from being standards compliant.

It's only a lot of work the first couple of times, soon enough you get the hang of it and it becomes second nature. Developing with web standards is actually much easier then without (if the standards are implemented correctly in the browser).

If you use tables for content layout you are not creating a very accessible website.

Ask any person who uses a screen reader on a regular basis what they prefer.

Tables maybe more likely to display correctly but CSS can also be made to display correctly with a little patience.

hey ph3n0m,

You see, I don't view it as coding for mozilla/firefox. I view it as coding for standards compliant browsers.

What's the difference?

Well, if everybody codes for standards compliant browsers then browser developers will be forced to produce standards compliant browsers.

That way, there will be less and less worries about how sites look in different browsers as we move forward.

As far as IE is concerned, IE has made positive steps in supporting standards, and I while the differences between IE and other browsers is annoying, I think progress is being made.

Yes IE still has the majority share and so it's important to ensure your site works in IE.

However I remember learning to design using tables and it was not that much different to learning to design using web standards. Surely you remember the horrible issues between NN and IE in table design back in the day?

In other words I think there is a learning curve to get into standards compliant development, but I think it's worth it to try and put the majority of cross browser issues behind us.

I'm realistic enough to realise there will always be cross browser issues, but I think good progress is being made.

As for what I consider a web standard design? One that validates.
However, as I stated I give myself some leeway when designing - unless, as Adam said, the client has requested a fully compliant site.

I hope this answers your questions... feel free to come back with your view on all this!

Cheers!
Frank

ha ha - evilhomer got there before me.

In addition to my post I second evilhomer's points!

I would say until there is a dramatic increase, the Firefox is still going to lag behind IE, no matter what the "experts" say. That is, unless there is a visible and sudden increase in the number of Firefox users, IE will still be number one

I wait with baited breath, but I aint holding it

and yet IE is still number 1 by a significant margin

and yet as far as we are lead to believe, most if not all current IE hacks will have to be either removed or redone when IE7 comes out

you said it..... "if the standards are implemented correctly"


well I for one can create a cross browser/platform website that works in most browsers (old and new) and it wouldnt necessarily be standards compliant

but that progress is slow

but that doesnt necessarily mean it will work cross browser/platform