| them
| down. An alternative would be to have different css files for
| different
| browsers and declare the css to load as a variable in your app. It
| will
| have the same result and the css files are not parsed by cf. I usually
| have a css-file for recent browsers and a simple one for older
| browsers.
Pascal, I am not at all afraid of the processing needed, these files will be
very lightweight in terms of logic, and they should (hopefully) only be
downloaded once for the whole site. Part of the point is that maintaining
separate stylesheets for different browsers and then run a browser-check on
every page is nothing something I would like to maintain... :)
Jochem had a good point with the headers as well, thanks!
I guess the next step is to output the .js include files that I sometimes
use as cf... !
/Hugo
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
