> Respect what you say Christian - very much my thinking for I already build
> using no-hack no-JS cross-browser sites. However, once I saw a recent post
> (forget where) that remarked on dynamically separating styles by modifying
> the <html> tag according to browser type, all this caught my interest.
Nothing against that, however, a class is the wrong approach :-) The
other problem I see with this is that it bloats CSS unnecessarily as
you'd need to add a lot of
#MSIE6 body{}
#Opera body{}
and so on...
> I can see this method being useful for large or dynamic sites that must meet
> accessibility validation and in strongly structured sites. I've lost all
> hope of browser manufacturers playing the standards game so by placing a
> file on my servers and providing an API to it within my developments I can
> keep an easier track of browsers and their CSS quirks. In theory it offers
Seems a bit overkill for a lot of pages. TJK had some good ideas that
work for smaller sites:
http://tjkdesign.com/articles/branching.asp
This also has the benefit that you keep the hacks contained in own
documents. I simply don't see the point of using markup for browser
branching. Even a pre-processor for your CSS files that checks and
only grabs the CSS inside comments like
/* Start:MSIE */
/* End:MSIE */
would make more sense (Server Side Cross Browser Conditional Comments
- let's call them SSCBCC to create a new buzzword! so to say)
> quite a lot for portable, teletext and other devices too. So I thought I'd
> play and see if the theory meets fact - and remove a lot of need for
> addressing browser CSS foibles. It seems to assist with getting rid of
> unnecessary JS too (I find CSS horizontal menus that require JS severely
> distasteful).
I dislike dynamic menus that assume I have Opera to give me keyboard
access - something that is much easier possible with JS.
> Also, I had a thought that by "globalising" browser issues in one place/file
> I could more easily knock off CSS issues as future browsers resolve them
> without turning my two brain cells to dust.
That would involve putting that file somewhere very accessible to
anyone - like wikipedia or even better akamai. The question is also
how would you recognise and distinguish future browsers from the
current ones. The bug IMHO is neither the browser nor the specs, it is
the disbelief that a good web site looks the same everywhere. Most CSS
bugs are not showstoppers - unless you planned for an inflexible site
from the start.
--
Chris Heilmann
Book: http://www.beginningjavascript.com
Blog: http://www.wait-till-i.com
Writing: http://icant.co.uk/
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
IE7b2 testing hub -- http://css-discuss.incutio.com/?page=IE7
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
