Except that then that stylesheet gets cached (more likely cached on the
proxy) and you have the same problem all over again.
Jake
On 19/9/2005, "Geoff Pack" <[EMAIL PROTECTED]> wrote:
>
>John,
>
>There's no need for a server-side include to do this. Just use a linked
>stylesheet to import the real stylesheet:
>
>i.e. in your html pages:
>
> <link rel="stylesheet" type="text/css" media="screen" title="Default"
> href="screen.css">
>
>in screen.css:
>
> @import url("nav.css");
> @import url("main.css");
> ...
>
>This has the additional benefit of excluding NS4.
>
>cheers,
>Geoff
>
>
>
>> -----Original Message-----
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] Behalf Of
>> [EMAIL PROTECTED]
>> Sent: Monday, 19 September 2005 11:17 AM
>> To: [email protected]
>> Subject: [WSG] The Big Lie about CSS
>>
>>
>> I was thinking this morning that we constantly tell people two things
>> about CSS, as in this wonderful presentation:
>>
>> http://www.hotdesign.com/seybold/ (pages 9 and 10)
>>
>> we tell them
>>
>> a) it's more efficient because the style sheet only gets
>> downloaded once!
>>
>> and then we tell them
>>
>> b) you can reformat your whole site just by changing the CSS file!
>>
>> and what, we just hope nobody notices that they contradict each other?
>>
>> In other words, what do you do to ensure that your newly-updated
>> stylesheet isn't cached? In the past, I've resorted to doing this:
>>
>> <!--#include virtual="link-rel.txt" -->
>>
>> where link-rel.txt contains
>>
>> <link rel="stylesheet" href="/css/2005-09-18.css" type="text/css">
>>
>> so that when changes are made, I can just change the include to refer
>> to "2005-09-19.css" and be sure there's no caching going on. Or, in
>> the case of a major browser-hanging bug, "2005-09-19-11-15AM.css" ...
>> ------------------------------------------------------------
>> "Have You Validated Your Code?"
>> John Horner (+612 / 02) 8333 3488
>> Developer, ABC Kids Online http://www.abc.net.au/
>> ------------------------------------------------------------
>> ******************************************************
>> The discussion list for http://webstandardsgroup.org/
>>
>> See http://webstandardsgroup.org/mail/guidelines.cfm
>> for some hints on posting to the list & getting help
>> ******************************************************
>>
>>
>******************************************************
>The discussion list for http://webstandardsgroup.org/
>
> See http://webstandardsgroup.org/mail/guidelines.cfm
> for some hints on posting to the list & getting help
>******************************************************
>
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
