Greg,
( I believe that... ) You may avoid that caching by adding an expire date to the css http
header so the browser will be forzed to perform the download.
2 cents.
Gb.
2008/9/9, Greg Smith <gsmith@gregsmith.com>:
> On Tue, 9 Sep 2008, David Fetter wrote:
>
>> The standard doesn't number them the way you're doing, and I need to be
>> able to override it. Just to clarify, if somebody doesn't use actual
>> HTML and the given classes for <li> tags, nothing will change.
>
> I'm not familiar enough with CSS to say whether that's true or not. I do
> suspect there was a way to accomplish this for a page without touching
> common.css like that. I would have certainly asked that question here and
> waited a while for feedback before touching anything.
>
> What I am uncomfortable with is the way this page was edited. The
> common.css file is cached by browsers for a long time. See
> http://en.wikipedia.org/wiki/Wikipedia:Catalogue_of_CSS_classes for
> comments about that. Looks like it was about three hours you experimented
> there to get that right. It really bothers me that changes that impact
> the whole site were made like that. Someone who happened to grab one of
> your intermediate files during that period is stuck with that one for the
> next month unless they know the proper reload trick. What if you'd have
> accidentally broken something?
>
> I personally would never touch common.css with an untested change on this
> Wiki. I have a private MediaWiki installation I use for experiments like
> that, and I'd only roll out a system-wide change on the PG Wiki that had
> been confirmed to work there first. In this case, I don't think you
> actually did any harm, but the way this all happened is not something I'd
> like to see repeated.
>
> --
> * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
>
> --
> Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-www
>
--
Guido Barosio
-----------------------
http://www.globant.com
guido.barosio@globant.com
