One would imagine that Firefox 3.0.5 would act the same in both Windows and Mac OS X. Well, in theory they should, right? At least, in my head, I think they should. After all, the same browser in different operating systems should render HTML in the same way. One would expect that. But that’s only theory. In practice, that doesn’t happen all the time.
I admit it, it happens 99% of the time. 99% comes directly from my gut and from my experience. We haven’t done a special study in Aycron about it. But that’s my feeling. As far as I know, I’ve seen this problem twice in the last three months. And we’ve written a lot of HTML/CSS in that time. That is not very often. But it still happens. That 1% of the times is very annoying because it takes a lot of time to come up with a workaround that works in every possible combination of FF, IE6, IE7, Safari and Windows, Mac OS X.
So, in theory, FF 3.0.5 should do the same in Windows or Mac OS X. In practice, it doesn’t. However, the percentage of times is very low. But the problem is still there. Believe me, I have triple (if not more) checked and there is a problem between FF for Windows and FF for Mac OS X, which is another headache for all of us developing sites for FF, IE6, IE7 and Safari.
cross browser compatibilities: theory vs. practice
One would imagine that Firefox 3.0.5 would act the same in both Windows and Mac OS X. Well, in theory they should, right? At least, in my head, I think they should. After all, the same browser in different operating systems should render HTML in the same way. One would expect that. But that’s only theory. In practice, that doesn’t happen all the time.
I admit it, it happens 99% of the time. 99% comes directly from my gut and from my experience. We haven’t done a special study in Aycron about it. But that’s my feeling. As far as I know, I’ve seen this problem twice in the last three months. And we’ve written a lot of HTML/CSS in that time. That is not very often. But it still happens. That 1% of the times is very annoying because it takes a lot of time to come up with a workaround that works in every possible combination of FF, IE6, IE7, Safari and Windows, Mac OS X.
So, in theory, FF 3.0.5 should do the same in Windows or Mac OS X. In practice, it doesn’t. However, the percentage of times is very low. But the problem is still there. Believe me, I have triple (if not more) checked and there is a problem between FF for Windows and FF for Mac OS X, which is another headache for all of us developing sites for FF, IE6, IE7 and Safari.