First off, here are my referenced pages in .txt docs:
ASP.NET Display page: <!-- m --><a class="postlink" href="http://www.douglas-county.com/test_folder/page.txt">http://www.douglas-county.com/test_folder/page.txt</a><!-- m -->
Firefox Stylesheet: <!-- m --><a class="postlink" href="http://www.douglas-county.com/test_folder/ff1.txt">http://www.douglas-county.com/test_folder/ff1.txt</a><!-- m -->
IE 6.0 Stylesheet: <!-- m --><a class="postlink" href="http://www.douglas-county.com/test_folder/ie6.txt">http://www.douglas-county.com/test_folder/ie6.txt</a><!-- m -->
Footer Article: <!-- m --><a class="postlink" href="http://www.alistapart.com/articles/footers/">http://www.alistapart.com/articles/footers/</a><!-- m -->
I'm attempting to create an all-new site for us using CSS positioning exclusively instead of tables. After several bits of advice, I decided to detect the users browser type, and give them the appropriate stylesheet instead of using a bunch of hacks that could become a pandora's box of maintenance.
I'm almost done with the creation of a few stylesheets based on the user's browser type (using server-side browser detection), but I'm having two strange issues that I've not been able to solve:
1) IE issue - The display page is showing a few pixels of space below the leftnav. I think that it's the "background-color" property on one of the stylesheet properties, but I can't figure out why it only does that in IE (besides the usual issue of IE being a pain in the a** to develop with).
2) Footer Issue (in all browsers) - I'm trying to follow the included article from A List Apart, but my footer is not showing up at the bottom of the window for IE or Firefox.
If anyone can give me an idea on what could be causing these issues in my included stylesheets, it would be greatly appreciated. Thanks for any & all help.So you're going to code twice for each page, eh? Bad advice. You shouldn't have to do that. Just code for FF and adjust for IE. Shouldn't be too complicated.I'm with drhowarddrfine. You think using a few hacks is a nightmare for maintenance? What do you think it'll be like when you have to change the same thing on separate style sheets? I think you got some bad advice before.hhmmm. Well, it wouldn't be a big deal for me to switch at this point, since the two stylesheets are very similar except for the margins. And I have seen conditional properties used in CSS. But since you're both suggesting that I use that method instead of browser detection, what's the best, most proper, and easiest way to accomplish that within one stylesheet for several browser types?
P.S. Thanks for your input on this, as this is the time for me to get it right...as opposed to a year from now
Can you just post a link to the (live) page? Then I'll see what can I do....actually it's on an internal test-server, so I can't do that right now. But I'll move a copy to a test directory on our web-server. I'll let you know when I get that done later today so that you can check it out for me. Thanks for your help.While I'm working on these test pages, I thought that this might be a good discussion between developers on this forum. Is it better to use server-side browser detection to give users the appropriate stylesheet, or is it better to use one main stylesheet with several browser hacks?
I'd like to know what the pro's & con's are for each setup, which setup would take less maintenance in the future, and which is the most proper way to accomplish this task. I hope to hear some good opinions. Thanks.You might want to start a new thread for that - with an appropriate title. I think you'll get some opinions that way.Good point...I'll do that. Thanks BonRouge.
ASP.NET Display page: <!-- m --><a class="postlink" href="http://www.douglas-county.com/test_folder/page.txt">http://www.douglas-county.com/test_folder/page.txt</a><!-- m -->
Firefox Stylesheet: <!-- m --><a class="postlink" href="http://www.douglas-county.com/test_folder/ff1.txt">http://www.douglas-county.com/test_folder/ff1.txt</a><!-- m -->
IE 6.0 Stylesheet: <!-- m --><a class="postlink" href="http://www.douglas-county.com/test_folder/ie6.txt">http://www.douglas-county.com/test_folder/ie6.txt</a><!-- m -->
Footer Article: <!-- m --><a class="postlink" href="http://www.alistapart.com/articles/footers/">http://www.alistapart.com/articles/footers/</a><!-- m -->
I'm attempting to create an all-new site for us using CSS positioning exclusively instead of tables. After several bits of advice, I decided to detect the users browser type, and give them the appropriate stylesheet instead of using a bunch of hacks that could become a pandora's box of maintenance.
I'm almost done with the creation of a few stylesheets based on the user's browser type (using server-side browser detection), but I'm having two strange issues that I've not been able to solve:
1) IE issue - The display page is showing a few pixels of space below the leftnav. I think that it's the "background-color" property on one of the stylesheet properties, but I can't figure out why it only does that in IE (besides the usual issue of IE being a pain in the a** to develop with).
2) Footer Issue (in all browsers) - I'm trying to follow the included article from A List Apart, but my footer is not showing up at the bottom of the window for IE or Firefox.
If anyone can give me an idea on what could be causing these issues in my included stylesheets, it would be greatly appreciated. Thanks for any & all help.So you're going to code twice for each page, eh? Bad advice. You shouldn't have to do that. Just code for FF and adjust for IE. Shouldn't be too complicated.I'm with drhowarddrfine. You think using a few hacks is a nightmare for maintenance? What do you think it'll be like when you have to change the same thing on separate style sheets? I think you got some bad advice before.hhmmm. Well, it wouldn't be a big deal for me to switch at this point, since the two stylesheets are very similar except for the margins. And I have seen conditional properties used in CSS. But since you're both suggesting that I use that method instead of browser detection, what's the best, most proper, and easiest way to accomplish that within one stylesheet for several browser types?
P.S. Thanks for your input on this, as this is the time for me to get it right...as opposed to a year from now
Can you just post a link to the (live) page? Then I'll see what can I do....actually it's on an internal test-server, so I can't do that right now. But I'll move a copy to a test directory on our web-server. I'll let you know when I get that done later today so that you can check it out for me. Thanks for your help.While I'm working on these test pages, I thought that this might be a good discussion between developers on this forum. Is it better to use server-side browser detection to give users the appropriate stylesheet, or is it better to use one main stylesheet with several browser hacks?I'd like to know what the pro's & con's are for each setup, which setup would take less maintenance in the future, and which is the most proper way to accomplish this task. I hope to hear some good opinions. Thanks.You might want to start a new thread for that - with an appropriate title. I think you'll get some opinions that way.Good point...I'll do that. Thanks BonRouge.