Paul S
asked on
CSS only works in IE and not Navigator.
please see this question:
http://oldlook.experts-exchange.com/questions/21131444/More-compatible-website.html
I thought it was a php problem, but now i think it is a css problem. Please help!. if you can solve it i will give you points from both of these questions.
http://oldlook.experts-exchange.com/questions/21131444/More-compatible-website.html
I thought it was a php problem, but now i think it is a css problem. Please help!. if you can solve it i will give you points from both of these questions.
ASKER
i agree very much! thank you. i already build my sites for 800 x 600 and higher. I also build them for newer browser and not older ones. My problem is HOW do i get my code to work on mozilla engines? what should i avoid? i am using div tags and css to position my website. i think the problem is somewhere in there. maybe you can find it.
www.paulscomputerservice.net
www.paulscomputerservice.net
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
hey click on the link in my question. Another guy kind of said the opposite. to use CSS and not tables. go look.
This question is a matter of preference. You can go ahead and do all your layout using CSS positioning if you want. But what it comes down to is compatibility.
Tables have been part of HTML since the beginning. How they are displayed across browsers is pretty much standard now. CSS positioning is relatively new in web browsers. Additionally, many browsers do not support CSS positioning. Therfore, if you choose CSS positioning you are more likely to experience incompatibilities than if you chose a table layout. If you really want to use CSS positioning than you should, but be aware that these types of issues will come up.
Good luck!
Tables have been part of HTML since the beginning. How they are displayed across browsers is pretty much standard now. CSS positioning is relatively new in web browsers. Additionally, many browsers do not support CSS positioning. Therfore, if you choose CSS positioning you are more likely to experience incompatibilities than if you chose a table layout. If you really want to use CSS positioning than you should, but be aware that these types of issues will come up.
Good luck!
Strangely most of the positioning attributes have been around for about 5 years now, and although I'm quite comfortably applying them across multiple browser-flavours, still I hear developers say that it's not working the coherently. Simple rules to follow:
The position of an element can be determined in several ways:
static, according to text-flow.
absolute, according to the first ancestor which has a position (the top-most element always has a position, that would be either html or body, depending on the browser)
relative, offset derived from the elements original static (see above description) position. This also preserves it's original space and position within the text-flow.
float, the only hardball in the park. vertical position is determined by textflow, the rest according to it's ancestors. However the way the ancestor behaves is not consitent.
These three rules apply to any and all major brands, exceptions apply when you start constructing rather complicated combinations, but in 80% of those cases you're talking about designs that would not render in tables without miles of codesoup.
My guess is that your troubles will mostly derive from something entirally different, the way a box is rendered and specifically resized. This is something that's quite bothersome as IE renders it rather differently from the rest of the crowd. Having said that I'm now going to have a look at your site and questions to see if I can find a solution for them.
Best regards,
Martin
The position of an element can be determined in several ways:
static, according to text-flow.
absolute, according to the first ancestor which has a position (the top-most element always has a position, that would be either html or body, depending on the browser)
relative, offset derived from the elements original static (see above description) position. This also preserves it's original space and position within the text-flow.
float, the only hardball in the park. vertical position is determined by textflow, the rest according to it's ancestors. However the way the ancestor behaves is not consitent.
These three rules apply to any and all major brands, exceptions apply when you start constructing rather complicated combinations, but in 80% of those cases you're talking about designs that would not render in tables without miles of codesoup.
My guess is that your troubles will mostly derive from something entirally different, the way a box is rendered and specifically resized. This is something that's quite bothersome as IE renders it rather differently from the rest of the crowd. Having said that I'm now going to have a look at your site and questions to see if I can find a solution for them.
Best regards,
Martin
I had a long hard look at your website and I think you really need to reduce your html code into something far more simplified. I did start on a template, I'll try and do some more work on it this weekend but here's a preview:
http://www.windgazer.nl/eexchange/Q_21136870b.html
This is coded to work in all major brand CSS2 browsers and modified slightly to support IE, however, when finished it should work fine browsers not supporting css, it'll look less slick, but it should still be useable. I'll come back with more info and explenations on what I'm aiming for.
Of to dinner,
Martin
http://www.windgazer.nl/eexchange/Q_21136870b.html
This is coded to work in all major brand CSS2 browsers and modified slightly to support IE, however, when finished it should work fine browsers not supporting css, it'll look less slick, but it should still be useable. I'll come back with more info and explenations on what I'm aiming for.
Of to dinner,
Martin
ASKER
WOW! that is awesome that you are willing to spend time and help my build my site again. I REALLY appriciate it. I will give you all my points and be in your debt forever!
ASKER
i switched over to tables like you said. my site works great now. thanks. post a comment here
http://oldlook.experts-exchange.com/questions/21131444/More-compatible-website.html
and you can have those points too.
http://oldlook.experts-exchange.com/questions/21131444/More-compatible-website.html
and you can have those points too.
You can try to accomodate everyone, but what you will find is that there are too many "everyones" to make happy. I tend to design for a minimum resolution of 800 X 600, and target users who have IE 5+ or Netscape 6+. Going any further back for me is a waste of time since the inconsistencies get greater the further you go back.
I hope this helps!
Best of luck