Hi Chris,
> So when it comes to css3 is it really so ugly? If you really want an answer to that, unfortunately yes... and no its not just gradients. > So say I was trying to add browser specific css to my layout component what > would people suggest as the best strategy? Browser detection is pretty awful, as its a moving target and not perfectly accurate, but granted in some cases a necessary evil... avoid it if you can. Its not uncommon to simply specify all the styles for the various browsers because those that are not understood will simply be ignored... be sure though that they are not understood or you might encounter a nasty surprise or two. In your example there should be no need for detection. Cheers, Peter ----- Original Message ----- From: "Chris Collins" <chris...@me.com> To: "Tapestry users" <users@tapestry.apache.org> Sent: Tuesday, 6 December, 2011 7:48:57 AM Subject: smarter css So when it comes to css3 is it really so ugly? Ok perhaps its just things like gradients: http://ie.microsoft.com/testdrive/graphics/cssgradientbackgroundmaker/default.html So in the microsoft example above for getting a gradient background you have to use different css properties per browser. So say I was trying to add browser specific css to my layout component what would people suggest as the best strategy? Random thoughts: - You can't tml-ify css, if you could then you could condition parts of it by browser right? - Would you create a series of browser specific css assets then build inject them directly into the layout page? Clearly I don't have a clue :-} again sorry for dumb questions. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
