Prev: Parallels and Boot Camp integration
Next: IS THE JURY IN? Should I update from 10.3.9 to 10.5.x?
From: dorayme on 21 Jun 2008 04:07
Running a home server I have noticed that iCab (but not Safari) fails to
load recent changes to linked CSS files. I have the prefs set rationally
and as recommended by iCab "Load files from best source" which depends
on the server notifying the browser that there has been an update. The
server (that comes with OS X) obviously does the job well for HTML files
because, for example, inline CSS instructions are immediately
implemented.

Not quite sure if this is an iCab bottleneck or a server one, is there
some config setting for the home server to tell browsers that hey, the
css file has changed. Beyond my pay grade to know which or how to
improve situation.

I know I can set iCab to always get from the web rather than cache, that
is a fix but with some downside as you will appreciate.

--
dorayme
From: Alexander Clauss on 21 Jun 2008 06:55
dorayme <doraymeRidThis(a)optusnet.com.au> wrote:

> Running a home server I have noticed that iCab (but not Safari) fails to
> load recent changes to linked CSS files. I have the prefs set rationally

In case you're using MacOSX 10.5.x, then this issue is caused by a bug
of "Leopard". Deleting the Web Cache of iCab should fix this problem for
a while.

--
Alexander
From: dorayme on 21 Jun 2008 08:08
In article <1iivyh3.j3kf2q1ofpdhcN%aclauss(a)hrzpub.tu-darmstadt.de>,
aclauss(a)hrzpub.tu-darmstadt.de (Alexander Clauss) wrote:

> dorayme <doraymeRidThis(a)optusnet.com.au> wrote:
>
> > Running a home server I have noticed that iCab (but not Safari) fails to
> > load recent changes to linked CSS files. I have the prefs set rationally
>
> In case you're using MacOSX 10.5.x, then this issue is caused by a bug
> of "Leopard". Deleting the Web Cache of iCab should fix this problem for
> a while.

No, I have been using Tiger 10.4.10

You know, Alexander, this is a problem I think I have had for a very
long time with iCab, from many versions back. It is not the end of the
world but I am curious as to why Safari detects it so quickly but not
iCab. I will make some further tests with other browsers.

I have no idea how Safari always seems to know the css has been changed.

Be nice if one could set prefs to cache images only? They are the big
hog.

--
dorayme
From: Sander Tekelenburg on 21 Jun 2008 09:20
In article
<doraymeRidThis-22CC44.22084521062008(a)news-vip.optusnet.com.au>,
dorayme <doraymeRidThis(a)optusnet.com.au> wrote:

> In article <1iivyh3.j3kf2q1ofpdhcN%aclauss(a)hrzpub.tu-darmstadt.de>,
> aclauss(a)hrzpub.tu-darmstadt.de (Alexander Clauss) wrote:
>
> > dorayme <doraymeRidThis(a)optusnet.com.au> wrote:
> >
> > > Running a home server I have noticed that iCab (but not Safari) fails to
> > > load recent changes to linked CSS files. I have the prefs set rationally
> >
> > In case you're using MacOSX 10.5.x, then this issue is caused by a bug
> > of "Leopard". Deleting the Web Cache of iCab should fix this problem for
> > a while.
>
> No, I have been using Tiger 10.4.10
>
> You know, Alexander, this is a problem I think I have had for a very
> long time with iCab, from many versions back.

Confirmed [Mac OS X 10.4.11]. This was introduced in iCab 4. The only
way to get it to see that the server's external CSS file is newer than
the cached one is to Shift-click the reload button (Cmd-Shift-R still
does nothing). There's some evidence that this is not a network issue,
as getting iCab 4 to apply certain settings changes, like en/disabling
javascript or plugins or adding/changing filters, also requires a
Shift-click on the Reload button.

For general browsing this might not be a big issue, but when you're
developing a site it can get quite annoying. Perhaps it would help if
these cache options would be available through the Filter Manager, so
you can use a different cache settings for sites you're developing. (I
rely on the Filter Manager to ensure that my user CSS is disabled on
sites I develop, for instance).

[...]

> I have no idea how Safari always seems to know the css has been changed.

Safari provides far fewer configuration options. It probably simply
behaves more like iCab's "always load files from the web" cache option.

--
Sander Tekelenburg, <http://www.euronet.nl/~tekelenb/>

Mac user: "Macs only have 40 viruses, tops!"
PC user: "SEE! Not even the virus writers support Macs!"
From: dorayme on 24 Jun 2008 07:21
In article <user-5ECD42.15203721062008(a)textnews.euro.net>,
Sander Tekelenburg <user(a)domain.invalid> wrote:

> In article
> <doraymeRidThis-22CC44.22084521062008(a)news-vip.optusnet.com.au>,
> dorayme <doraymeRidThis(a)optusnet.com.au> wrote:
>
> > In article <1iivyh3.j3kf2q1ofpdhcN%aclauss(a)hrzpub.tu-darmstadt.de>,
> > aclauss(a)hrzpub.tu-darmstadt.de (Alexander Clauss) wrote:
> >
> > > dorayme <doraymeRidThis(a)optusnet.com.au> wrote:
> > >
> > > > Running a home server I have noticed that iCab (but not Safari) fails to
> > > > load recent changes to linked CSS files. I have the prefs set rationally
> > >
> > > In case you're using MacOSX 10.5.x, then this issue is caused by a bug
> > > of "Leopard". Deleting the Web Cache of iCab should fix this problem for
> > > a while.
> >
> > No, I have been using Tiger 10.4.10
> >
> > You know, Alexander, this is a problem I think I have had for a very
> > long time with iCab, from many versions back.
>
> Confirmed [Mac OS X 10.4.11]. This was introduced in iCab 4. The only
> way to get it to see that the server's external CSS file is newer than
> the cached one is to Shift-click the reload button (Cmd-Shift-R still
> does nothing). There's some evidence that this is not a network issue,
> as getting iCab 4 to apply certain settings changes, like en/disabling
> javascript or plugins or adding/changing filters, also requires a
> Shift-click on the Reload button.
>
> For general browsing this might not be a big issue, but when you're
> developing a site it can get quite annoying. Perhaps it would help if
> these cache options would be available through the Filter Manager, so
> you can use a different cache settings for sites you're developing. (I
> rely on the Filter Manager to ensure that my user CSS is disabled on
> sites I develop, for instance).
>
> [...]
>
> > I have no idea how Safari always seems to know the css has been changed.
>
> Safari provides far fewer configuration options. It probably simply
> behaves more like iCab's "always load files from the web" cache option.

Thanks for this info, if it arises again I will try your keystroke
suggestions. For some reason, now I return to this issue, I cannot
reproduce the trouble! When viewing a site on my home server, changing
some heading CSS <h1>...</h2> in a linked CSS sheet was immediate on
reload, iCab set for load files from 'best source' and use caches ticked.

--
dorayme
 |  Next  |  Last
Pages: 1 2
Prev: Parallels and Boot Camp integration
Next: IS THE JURY IN? Should I update from 10.3.9 to 10.5.x?