PSD to XHTML: Importance of Browser Compatibility

admin on Apr 20th 2009 with 22 comments

The increasing importance of PSD to XHTML conversion cannot be negated. It is an intrinsic part of Website Designing and holds a heavy weightage. It also goes beyond saying that Internet has spread its root in a diverse fashion and does not limit itself to Home PC and Systems.

The browsers are adding up in the queue, and with the arrival of every new or improved browser, the coding criteria also changes. Earlier the coder has to fix his attention to limited browsers, but the present XHTML coding rules simply outcast any leniency with browser compatibility.

The well known and highly used browsers are IE (with its different versions), Mozilla and Safari. Many people are comfortable with Mozilla because of its user friendliness (each link opening in different tab with horizontal structure), while many find IE better. Safari is a comparatively new browser with different specifications than IE or Mozilla; and then there is Google Chrome from Google. Hence while code testing, it becomes important to check the pages in all the different browsers from common to uncommon ones. You cannot just leave the compatibility issue with Opera, Opera Mini, Netscape and other browsers because few number of people use it. Your prospective clients, who are sitting poles apart, may very well be browsing your website through Netscape or Opera. And who knows that he might very well turn into a regular business client!

How to Make them Browser Compatible
After knowing the importance, the point in question is how to make the site browser compatible. A thorough XHTML programmer knows all the coding formulae. If you however choose to begin the coding with basic XHTML understanding you possess, it is important to note that not all the browsers can be made XHTML compatible. IE 5 for instance, has no in-built functionality to support Div, and hence does not support XHTML.

It is therefore important to choose a set coding standard that goes well with all the preferred browsers. But at the same time, there might be cases where a particular specified content attains perfect visibility in one browser, and appears deformed in another. A textual paragraph for instance, with a defined width, color and font specifications might not come out fine in two different browsers. In this case, some programmers use Browser Hack to even out the content in both the browsers. But the use of Hacks is not recommended and is avoided to the last as it does not signify browser compatibility.

A little knowledge is very dangerous. It is always a safe bet to outsource the design work to XHTML Conversion firms who are well versed with the ins and outs of XHTML coding standards.

Hope you liked the post. Social bookmarking and comments are welcome as ever

22 Responses

Johnson Koh

Apr 23rd , 2009

Agree with the points mentioning about the compatibility of various browsers. Safest bet is still outsourcing to XHTML Conversion firms for important websites.

So far the most problematic one is still Internet Explorer…sigh.

Leena

May 12th , 2009

Good Article.

Google Chrome Wallpapers

May 17th , 2009

I found your blog on google and read a few of your other posts. I just added you to my Google News Reader. Keep up the good work. Look forward to reading more from you in the future.

GarykPatton

Jun 16th , 2009

I have been looking looking around for this kind of information. Will you post some more in future? I’ll be grateful if you will.

Mahallo Media

Jun 29th , 2009

Thanks for this helpful article.

Josh Maxwell

Jun 29th , 2009

While I agree with your main point: browser compatibility. However, I disagree with some a few things. A few notable things: Netscape & IE5. Seeing as how they are no longer supported by their own originators, I don’t believe designers/developers should either. And, rightfully so. Microsoft has since put out 3 versions & IE5 is nearly off of it’s last leg. IE6, too, is well on it’s way to the grave, too (at least we all hope so)! Netscape, including AOL, mostly works/looks as sites should. I don’t see why we should spend extra time on nearly-dead-browser compatibility. Opera, on the other hand, in my opinion, seems to be steadily on the rise. And, as to outsourcing: if you don’t know what you’re doing, by all means outsource! I urge the designer-only’s out there to begin learning how to convert them over though themselves. It’s a handy thing to know, you can say you have one more skill (meaning more money in your pocket), and you’re not putting money into someone else’s pockets (more in your’s!). Still, I envy those who get to do nothing but design!

Flex Guy

Jul 1st , 2009

very nice article…keep on the good work

CrisBetewsky

Jul 6th , 2009

Some of us even don’t realize the importance of this information. What a pity.

workingforgoogle

Aug 14th , 2009

Thanks very much for posting such a great article. I’ve actually been searching for a long time for this.

amber jewellery

Aug 22nd , 2009

Well, I agree with author – better to outsource XHTML coding for company which specialize in this type of work. If anything is not working, you can always ring them and ask for fix. But sadly it’s a nightmare to do this by yourself. Agrgrrhhh!