Interbrowser compatibly driving me nuts.

[Reply]

@Stan_Shmenge

Is it really better than a decade ago? I could make a decent page that would render in all browsers then. Yeah we can do more now, but this shit is just insane. I am freaking over some small pixel shifts that Firefox is rendering for no reason that I can see.

My roomie uses Dreamweaver and thinks I am crazy to hand code my crap, and maybe he is right. He does awesome web pages and has a bunch of clients, but I want to know how it all works and do it in Notepad++

He makes money. I haven’t done this for a buck in years. Yeah, I am stubborn. I am not trying to do this for a living.

Dreamweaver has its place in the workflow, especially when you just want to get the rough draft up and running without having to manually adjust pixel values for every element. It never hurts to hand-check the results, though.

I wish all the manufacturers would just band together and declare a joint moratorium on new versions until every browser is 100% compliant with HTML6 and CSS4 – to the pixel.

[yabob]

For starters, you appear to want a single image as the background to that table. Why not do that, rather than trying to stitch images together? Then, if you want to display graphics as clickable items on top of it in the table cells, make them have transparent backgrounds.

[ZipperJJ]

One of the things that will help in IE and maybe Firefox too is to not put a line breaks between your td and image tags.

This:

<td><img src="image.jpg"/></td>

Not this:

<td>
<img src="image.jpg"/>
</td>

[tellyworth]

@Reply

And IMO standards compliance is vastly overrated. There are too many browser versions and too many undefined rendering ambiguities for the standards to have any real meaning. They’re kinda neat as sort of a baseline to work against, but useless for actual compatibility testing.

Agreed. I’ve found two good reasons to maintain standards compliance, particularly if you’re learning:

1. If you make a point of ensuring your code always validates, it means you can use the validator to easily find mistakes (like missed closing tags) as you make changes.

2. It makes it easier to get help. The first thing many people will do is run your code through the validator, and tell you to fix the validation errors first.