Newest Firefox & I.E. 6 Display Differences

Status
Not open for further replies.

Aequitas

New member
Feb 19, 2007
2,954
73
0
Canada
Strange I was just curious if anyone else has noticed a couple of cross browser issues when building your sites, my new site is almost done, well it'll never fully be done but its almost good enough to take online but I'm just doing a bit of clean-up work and tweaking it for cross-browser support and I've noticed a couple things when testing with the newest firefox and I.E. 6

First off Firefox is picky when it comes to your CSS, they like to have things in complete fucking order, you can do the same thing in a different way but Firefox seems to like it their way, which is ok because I.E. 6 finds it great no matter which way you do it, anyway thats one little minor issue, please firefox and you've already pleased I.E. 6

Now onto the real difference and that is SPEED, this new site is 100% database driven so their are a lot of calls to the database, well ok not a lot everything runs off the database but its strange because in Firefox the lot speed is a touch slow but in I.E. 6 its lighting fast, as if there were nothing to load haha.

Might have something to do with the way they cache the page or maybe my firefox settings are fucked up but just curious to see if anyone ever noticed that before?

I doubt it'll actually become an issue because I'm still going to tweak for the best database performance. So yeah nothing really education in this thread for us developers but just curious to see the thoughts of anyone doing cross-browser support.
 


I tend to code for Firefox and then fix for IE.
IE has far more issues than Firefox, Opera, or Safari.
The reason it's more lenient is because Microsoft ignores standards and does things its way. However, by ignoring standards they messed up the browser and ended up with tons of bugs. (Double padding on floats, height 1% hack, overflow hidden hacks, occasionally ignores margin, etc.)
 
I tend to code for Firefox and then fix for IE.
IE has far more issues than Firefox, Opera, or Safari.
The reason it's more lenient is because Microsoft ignores standards and does things its way. However, by ignoring standards they messed up the browser and ended up with tons of bugs. (Double padding on floats, height 1% hack, overflow hidden hacks, occasionally ignores margin, etc.)

haha how true, I've always usually testing for IE in the past and just recently started testing with Firefox first and wow, when you first code for IE, there are a ton of little fuck ups when you look at it in Firefox, I was just glad I thought my way through this project (Well somewhat), only had to change two or three tags for my entire website.
 
One thing about coding for multiple browsers, it plain sucks. I usually code in Firefox as well,then check in IE7, and then check in IE6. I'd have to say IE6 is just really annoying, and I'm being modest. IE7 does fix a lot of things, though.

Generally, if I get my code working in Firefox and IE7, chances are it'll work properly in Opera.
 
One thing about coding for multiple browsers, it plain sucks. I usually code in Firefox as well,then check in IE7, and then check in IE6. I'd have to say IE6 is just really annoying, and I'm being modest. IE7 does fix a lot of things, though.

Generally, if I get my code working in Firefox and IE7, chances are it'll work properly in Opera.

Yeah I don't cross check for much more then the newest Firefox, IE6 & 7, I figure the majority of the users will be using those browsers anyway as well I don't really take the time to create a liquid site, although I really should it just requires a bit more thinking, oh well for those newbies who still use a 640x486
resolution they'll have to do a bit of scrolling but I did leave some room for above and lower resolution (above & below 1024x768).
 
That's true, there's really no point to design for anyone lower than 1024x768
Around 3% of my traffic has 800x640 resolutions, and IMO it's not worth the sacrifice.

Also make sure you code in XHTML (dont bother with validating it)
The advantage of this is that IE properly renders padding with XHTML, so you don't need as many hacks and workarounds.
 
As others have mentioned I always code for FF then fix for IE

One of the biggest pains in my ass with IE is how it handles or rather...mishandles floats all the time. I end up having to put wrappers and containers around floats just to keep them in place and from wrapping down on the page all wierd and shit...
 
As others have mentioned I always code for FF then fix for IE

One of the biggest pains in my ass with IE is how it handles or rather...mishandles floats all the time. I end up having to put wrappers and containers around floats just to keep them in place and from wrapping down on the page all wierd and shit...

Yeah I've noticed that as well, float images in IE look great but then go over to Firefox and they are all over the place and all fucked up, but if you fix them in Firefox and look at them in IE they are still all good.

I'm definatly going to start using Firefox as my first browser test instead of the other ones.
 
Yeah I've noticed that as well, float images in IE look great but then go over to Firefox and they are all over the place and all fucked up, but if you fix them in Firefox and look at them in IE they are still all good.

I'm definatly going to start using Firefox as my first browser test instead of the other ones.

I put together a list of FF add ons that I use here: Links » Stanley Shilov (scroll down a bit)
grab them, trust me on this you won't regret it. Firebug and Web Developer toolbar are the most important ones
 
Status
Not open for further replies.