...

View Full Version : Firefox THEN Internet Explorer or vice versa



whackaxe
02-18-2005, 01:08 PM
today ive come across a bit of a challenge. for the last few webiste layouts ive done I've coded the page for Firefox then hacked it up with a seperate style sheet for it to work with IE6.

the problem i'm facing now is that ive created a page i can't hack using just CSS (haven't tried HTML yet, but i don't think it will solve my problems). i have two problems: i can't get divs to span 100% height. and the other is that depending on the browser width, one div moves by a pixel (seperate divs that make up one image. couldn't happen in a worse place on my page :p). like everyone else i'd love to stick a "Please view page with firefox" on the page and be done with it, but that doesn't go down to well with paying clients.

so, do you code for FF then hack the code for IE, vice versa, or do both at the same time bit by bit?

Sayonara
02-18-2005, 01:32 PM
I code to the W3C specs, then hack for IE and tweak for Konqueror.

There are a couple of good articles on A List Apart that deal with this kind of problem.

redoc
02-18-2005, 03:54 PM
It really depends on what / who your coding for. Any personal pages I do, I strictly do for firefox. However the last project at my job was primarily being done for in department use, so I know everyone will be using a 17" monitor, winXP, and IE. In this instance, I didn't even bother coding for any other browser.

Unfortunatly most users probably don't want to see any given webpage enough to download a new browser in order to see it. Plug-ins are scary enough for them :(

Sayonara
02-18-2005, 04:58 PM
Unless the day finally comes when all non-leaching web designers simply stop bowing down before IE, and don't bother to make allowances for it.

Viva la revolution! ;)

whackaxe
02-18-2005, 05:07 PM
yes, but what do you say to paying clients who say "this page looks 'funny'" alot of people don't even know what a browser is. for them its just "the" internet.

Sayonara
02-18-2005, 05:17 PM
If you code for IE because you have paying clients, you'd fall under the "leaching" category and therefore wouldn't know about the mighty rebellion of death until it was too late.

I understand the position people are in when they work for (or run) agencies that create web sites for non-web-literate people, but the fact is that they're taking money for doing bad things. "I can't educate my clients at the same time as providing the service they need" is just an excuse.

Sorry if this describes you, but I don't make the main part of my living off web design so I can afford strong opinions on it, lol ;)

Of course, the 'problem' with the is web that there is no regulatory body. If this were, say, the electricity industry*, we'd have someone like Elexon breathing down our necks all the time, and twice-yearly audits. That's enough to make anyone stick to standards, and Microsoft would be as likely to dominate the de facto standards arena as British Gas are to crawl back up to their monopoly status.


* if you aren't from the UK, substitute applicable organisation names.

Sayonara
02-18-2005, 05:19 PM
Oh, I should probably clarify - I'm not suggesting everyone should abandon coding for IE.

The majority of web sites are NOT corporate-owned. If the only sites that strictly required or displayed best in IE were corporate, and everyone else coded for inter-operability, the average web user would become more web-savvy through necessity.

WillGibson
02-18-2005, 06:25 PM
whackaxe, I mostly bounce from FF to IE to Opera to Moz as I work.

Sayonara, I hope you are trying to be funny and I just missed it...

If you code for IE because you have paying clients, you'd fall under the "leaching" category and therefore wouldn't know about the mighty rebellion of death until it was too late.

I understand the position people are in when they work for (or run) agencies that create web sites for non-web-literate people, but the fact is that they're taking money for doing bad things. "I can't educate my clients at the same time as providing the service they need" is just an excuse.

Sorry if this describes you, but I don't make the main part of my living off web design so I can afford strong opinions on it, lol ;)

Of course, the 'problem' with the is web that there is no regulatory body. If this were, say, the electricity industry*, we'd have someone like Elexon breathing down our necks all the time, and twice-yearly audits. That's enough to make anyone stick to standards, and Microsoft would be as likely to dominate the de facto standards arena as British Gas are to crawl back up to their monopoly status.


* if you aren't from the UK, substitute applicable organisation names.

Sayonara
02-18-2005, 06:52 PM
More like fantasising :D

WillGibson
02-18-2005, 07:04 PM
Fantasizing is good....unless it's in an auto...at high speed :)

oracleguy
02-18-2005, 08:20 PM
I typically code for FF then go back and then get it to at least mostly work in IE. If there are just minor cosmetic differences with IE, then I'll just leave it usually because it isn't worth the effort if it doesn't have to be exactly the same.

bdittmer
02-18-2005, 08:32 PM
You cannot set a div's height...period. Your best bet is to use a repeating image (probably a single white pixel if you background is white).

rmedek
02-18-2005, 08:35 PM
You cannot set a div's height...period. Your best bet is to use a repeating image (probably a single white pixel if you background is white).
???

div {
height: 100px;
overflow: many to choose from;
}


:confused:

gsnedders
02-18-2005, 10:44 PM
I code for Firefox, then Safari, [every other standard compilent browser], Lynx, IE.

brothercake
02-19-2005, 12:54 AM
I code for Firefox, then Safari, [every other standard compilent browser], Lynx, IE.
I used to do exactly that, but I've changed the order recently - because it's impossible to identify Opera specifically with CSS hacks - you can only go the other way.

So now I code for Opera, then tweak for safari/konqueror, then mozilla, then IE. That specific order reduces down to what (in my experience) is the smallest sequence of hacks by which you can still identify every major browser.

Like this:


/* opera 7 and 8 */
.foobar
{

}

/* safari/konqueror and mozilla */
*[class^="foobar"]
{

}

/* mozilla, but not safari/konqueror */
*[class^="foobar"]:lang(en)
{

}

/* ie */
* html .foobar
{

}

/* windows/ie */
@media screen, projection
{
* html .foobar
{

}
}

All inside a stylesheet which is filtered from legacy browsers using a delimited media attribute:


<link media="screen, projection" ...

Or if you don't want to bother with windows/ie5, use that link for an intermediate stylesheet, containing a filter hack and import statement:


@import "null?\"\{";
@import url("main.css");



EZ Archive Ads Plugin for vBulletin Copyright 2006 Computer Help Forum