>> That's a great way to prevent caching problems. But maintaining all those >> separate sections of the style sheet can be cumbersome. I suggest using a >> PhP Include to add one style sheet to each developing page. That way you can >> have embedded style sheets which won't get cached, and still work from one >> central style sheet.
> But you still loose one of the other advantages of using xhtml+css: the > bandwidth saving of having a cached css and only having the xhtml having > to be loaded... > > I'd recommend using the embedded stylesheet method only for testing, not > for live sites... > Patrick H. Lauke Absolutely. But the question was about caching during testing, so that was my work-around to the caching problem during testing. When ready to go live on-line, just move the css file reference up to the header using your choice of link or @import. There are ways to "force" IE MAC to refresh, or to set the prefs to "always" update, but it's still a highly finicky browser. My line of thinking is to by-pass the problem altogether by using the PHP "embedded" single style sheet trick during development, then importing it site-wide at launch. The bonus here is that you can build your final style sheet as you go, rather than having to compile all the separate ones from each page. Additional tangential info: There is a great article at fiftyfoureleven about stitching separate style sheets together using PHP: http://www.fiftyfoureleven.com/sandbox/weblog/2004/aug/css-php-organized-opt imized/ Kenneth Feldman [EMAIL PROTECTED] ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
