Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 15 of 15
  1. #1
    Senior Coder
    Join Date
    Jun 2002
    Location
    paris, france
    Posts
    1,216
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Firefox THEN Internet Explorer or vice versa

    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 ). 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?
    photoshop too expensive? use the GIMP! www.gimp.org

  • #2
    Regular Coder
    Join Date
    Oct 2004
    Posts
    256
    Thanks
    0
    Thanked 0 Times in 0 Posts
    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.

  • #3
    New Coder
    Join Date
    Jan 2005
    Location
    Iowa City
    Posts
    47
    Thanks
    0
    Thanked 0 Times in 0 Posts
    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
    PS - this is what part of the alphabet would look like if Q and R were eliminated.

  • #4
    Regular Coder
    Join Date
    Oct 2004
    Posts
    256
    Thanks
    0
    Thanked 0 Times in 0 Posts
    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!

  • #5
    Senior Coder
    Join Date
    Jun 2002
    Location
    paris, france
    Posts
    1,216
    Thanks
    0
    Thanked 0 Times in 0 Posts
    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.
    photoshop too expensive? use the GIMP! www.gimp.org

  • #6
    Regular Coder
    Join Date
    Oct 2004
    Posts
    256
    Thanks
    0
    Thanked 0 Times in 0 Posts
    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.

  • #7
    Regular Coder
    Join Date
    Oct 2004
    Posts
    256
    Thanks
    0
    Thanked 0 Times in 0 Posts
    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.

  • #8
    New Coder
    Join Date
    Dec 2003
    Location
    At work...still
    Posts
    57
    Thanks
    0
    Thanked 0 Times in 0 Posts
    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...
    Quote Originally Posted by Sayonara
    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.
    Why?
    Ok, but Why?

  • #9
    Regular Coder
    Join Date
    Oct 2004
    Posts
    256
    Thanks
    0
    Thanked 0 Times in 0 Posts
    More like fantasising

  • #10
    New Coder
    Join Date
    Dec 2003
    Location
    At work...still
    Posts
    57
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Fantasizing is good....unless it's in an auto...at high speed
    Why?
    Ok, but Why?

  • #11
    Rockstar Coder
    Join Date
    Jun 2002
    Location
    USA
    Posts
    9,074
    Thanks
    1
    Thanked 328 Times in 324 Posts
    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.
    OracleGuy

  • #12
    New to the CF scene
    Join Date
    Feb 2005
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts
    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).

  • #13
    Senior Coder
    Join Date
    Nov 2003
    Location
    Minneapolis, MN
    Posts
    2,879
    Thanks
    2
    Thanked 65 Times in 56 Posts
    Quote Originally Posted by bdittmer
    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;
    }



  • #14
    Senior Coder gsnedders's Avatar
    Join Date
    Jan 2004
    Posts
    2,340
    Thanks
    1
    Thanked 7 Times in 7 Posts
    I code for Firefox, then Safari, [every other standard compilent browser], Lynx, IE.

  • #15
    Senior Coder
    Join Date
    Jun 2002
    Location
    near Oswestry
    Posts
    4,508
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by Error 404
    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:
    Code:
    /* 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:
    Code:
    <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:
    Code:
    @import "null?\"\{"; 
    @import url("main.css");
    Last edited by brothercake; 02-19-2005 at 01:58 AM.
    "Why bother with accessibility? ... Because deep down you know that the web is attractive to people who aren't exactly like you." - Joe Clark


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •