If your CSS is not displaying correctly, why not use a PHP-generated CSS file? Your PHP file can detect the operating system and the browser that the client is using, and generate the correct CSS accordingly. If you then use mod_rewrite to mask the URL to a .css ending, it will be cached by the browsers. Also, put all your non-browser dependent CSS into a CSS file, and use the PHP one to only generate the CSS that is browser specific to reduce the amount of server-side parsing that needs to be done.
The only real time I use this appoach is because of IE (most notably because of its lack of min-width/max-width support).
Edit: I hit Submit before I was done by mistake...
Anyway, whenever I work on something, I want it to display correctly in all browsers without loss of content or functionality. I will continue to tweak the code until it works. (Right now I am reworking most of the HTML pages on my team's website into PHP ones with better graphics and better browser support). This is a major plus to using PHP instead of HTML to generate your pages: you can generate different code depending on the OS and browser of the clients to ensure that your page looks (and works) equally well in all browsers.
Be considerate to those who use Firefox, Opera, or Safari. Make your website one-hundred percent compatible in any browser.
Quote:
|
One thing that I have seen teams do is put a graphic or something that says "Best viewed in ________" Still-- your main goal should be to get something functional up in all browser types.
|
I like to create websites that work great in any browser and any screen size - I hate using fixed screen resolution sites. Because when ever you make fixed-res sites to 800px side, they look horrible at higher resolutions, and whenever someone creates a website to work perfectly at 1024px resolution, I hate scrolling sideways if I'm using an 800px screen. (My high school won't turn the screen resolutions above 800x600 on all its monitors and it drives me crazy, especially having to constantly scroll sideways
every single line to read stuff.)
I usually use 800x600 as a starting point - everything should be viewable in 800x600 screens without needing to scroll sideways. From there, I like to use a automatic resizing layout that will match the width of your browser screen up to a point (such as 1280px wide). This way, people in any screen resolution between 800px and 1280px widths (this will normally be about 95% of all traffic to your website) will be able to view your website. And by having the content max out at 1280px width, it makes the site still readible in those incredibly high resolution screens.
Yes, it does take more work to get everything to display correctly as it automagically resizes itself to match the browser window width, but in the end it behaves more "fluid" and displays like the user would want. (If a user has a browser window maximized with a 1024px resolution screen, they want to view the websites at a 1024px resolution.