Crappy websites

[thunderlizard]

secondly why don't people who create new browsers make sure they work with existing websites?

well, to be fair there are rather a lot of them!

Joel Spolsky's article is still the best I've seen to sum up the browser incompatibility problem:
http://www.joelonsoftware.com/items/2008/03/17.html

[bogeyman]

and that could be reduced to three lines if I cared to do so.

[original PM]

cheers for all the info

on a different note we are using EPISERVE? for what appear to be hsoting and content management - will this have any impact on different browser compatibility or not at all

and would it have any impact on any other area??

[Sysman]

IE6 is still a big fat fly in the ointment. It doesn't even nod to web standards and is still around in a lot of corporate environments (because using anything else will break their in-house intranet apps).

I had that with a previous clientco, starting a decade or more ago. Starting early on in the game, they had a wealth of intranet apps developed to work with Netscape, and installing MSIE was expressly forbidden.

That didn't stop the likes of the BBC (What? Promoting a commercial enterprise with my licence money? Heaven forbid, but that's what they did) insisting that I download MSIE for the "best experience".

When I (repeatedly) told such folks that I wasn't allowed to download and install MSIE they generally resorted to crud like "I wouldn't work for an employer that didn't allow me to run what I want". The really sad thing is that such folks clearly didn't understand what corporate IT is all about and yet they were in positions to spout their propaganda.

[Addanc]

Here's the recent stats from a website I babysit (and which gets lots of hits):

Perc. Browser Name Version
46.00% MSIE 8.0
37.00% MSIE 7.0
11.00% MSIE 6.0
4.00% Safari 4.0.3
2.00% Firefox 3.5.3

In previous looks at the same data, there's been more FF and less Safari.

EDIT: over 90% for Microsoft - depressing, eh?

Try these statistics - Firefox 46.6%.

[xoggoth]

Been doing a lot of conversion of DHTML interactives to work in Firefox etc recently. Been keeping some notes of the changes needed which might be of interest to somebody:-

http://www.gatekeeperel.co.uk/temp/firefox%20notes.txt

[NickFitz]

Been doing a lot of conversion of DHTML interactives to work in Firefox etc recently. Been keeping some notes of the changes needed which might be of interest to somebody:-

http://www.gatekeeperel.co.uk/temp/firefox%20notes.txt

Not sure why you were having problems with line-height in FF.

CSS:

#content {
    line-height: 2;
}

JavaScript:

document.getElementById("content").style.lineHeight = 2;

Note that line-height doesn't require units, and if you do supply them, it's best to use "em": if a user increases the font-size (either with Ctrl+ or by setting a minimum font-size in their preferences) then a line-height of, say, 12px would remain that size, resulting in lines overlapping. (This is in accordance with the CSS spec and IE will do the same.)

[Doggy Styles]

Dave, have you got to use this company? By now I'd have gone somewhere else.

[DaveB]

Dave, have you got to use this company? By now I'd have gone somewhere else.

Sadly yes I do. They are one of our corporate suppliers and I dont have a choice about using them.

[Doggy Styles]

Sadly yes I do. They are one of our corporate suppliers and I dont have a choice about using them.

Escalate it then. As high as you can go. They should not be taking the pi55 out of a captive market.