Erik Harris wrote: > At 05:09 PM 12/1/2007, Gunlaug Sørtun wrote: >> So, I would give browsers a complete Acid Stress Test, and hide >> same test from weaker browser and provide them with an alternative. >> > Aside from MSIE, how do you do this? You can use the MS-proprietary > commented "if" statements to provide alternate markup for various > versions of IE, which is useful for making up for IE's inability to > do things right, but what about Opera? Safari? Firefox pre-3.0? Is > there a straightforward way, aside from a JavaScript user agent > checker, to provide the different browsers different style info (or > markup)?
1: IE/win is given some extra styles... <http://www.gunlaug.no/contents/wd_additions_12.html> ...and maybe even a conditional comment in the source-code. I mention this here since it my method for feeding styles to IE isn't used all that much. 2: My design-base is Opera, and if there are some disturbing deviations between Opera, Firefox and Safari then I usually manage to give them something they all agree on. My method involves giving all browsers complete source-code and CSS even if neither standards nor the best browsers requires it. I rarely ever hack these browsers for anything serious, although my old hacks seem to hold up quite well... <http://www.gunlaug.no/contents/styles/target-browser.css> I expect these hacks to break since they are based on unusual use of standard selectors. Hopefully the CSS support has grown to a reasonable level to across the board when that happens, in which case the hacks just become redundant. Have to watch all such hacks though, and be prepared to correct them. > I suppose I should install Opera and Safari, too, but I just haven't > bothered (and at least Opera is good enough with standards > compliance that I wouldn't expect anything I'd be doing would break > it. You should have all major browsers available for testing even if they are pretty close on most CSS related stuff. Firefox 3.0b1 doesn't look too bad so far, but Fx 2 is/was a bit behind. > As a Windows user, Safari wasn't even a possibility until recently). IMO, Safari has been a bit weak when fed complex stuff, and the latest win-version doesn't seem too impressive either. Close enough for comfort though, and nice for testing some new stuff while waiting for the others. FWIW: I've decided not to upgrade my Mac, so it'll stay frozen in time with Safari 2.x until it dies of old age. It'll provide me with a platform to check other Mac-browsers on for a while, and I'm probably not the only one who won't upgrade Mac OS - for whatever reason. regards Georg -- http://www.gunlaug.no ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
