The Biggest Pain In Web Design

As I was polishing up my latest design, I couldn’t help but admire my genius. jQuery is so cool!

I sometimes get a little carried away and while taking my dinner, I leave a browser open on my desktop so that I can gaze at the awesome sites that are my Web Designs.

I’ve got an issue with Chrome that limits my capacity to open pages, so I have to hop around a bit with different browsers when I feel the need to gaze at my dreams. Only problem is that once I arrive, my dream quickly turns into a nightmare with my beautiful Web Design looking like a 3 year old designed it. I hate that crap!

I’m so comfortable with my abilities now, that I seldom reason beyond my finished design; especially when that design called for proven techniques instead of conceptual applications. In other words, I see the idea in my mind, I write it down and then see my design clearly displayed in my browser window as expected.

Only problem is that what one browser clearly displays, the next has little idea of what to do with “CLEARLY WRITTEN HTML & CSS”, even with the most simplest of designs.

It would be really nice if all I had to do was to provide warning to all of the evils of IE; however, most all the browsers, in one shape, way, or form get it wrong at one time or another. This is with designs standards that have been around for a while; I shutter to think what we are all in for with HTML5 and CSS3.

I’m still doing most of my work in Transitional, however, I am using HTML5 evermore for my simple designs, which I don’t believe was the intention of using HTML5. But the point is that, even with the simple stuff, I’m getting sorry rendering.

I’ll have to admit that beyond Chrome and Firefox I have little experience with browser CSS. However, for the life of me it seems that most of these good folks could get on the same page and lick this biggest of pains, that of “Cross-Browser Compatibility”.