On 10 Mar at 15:31, Tim Hill <t...@timil.com> wrote:

> In article
> <out-513a46b0.md-1.4.17.chris.yo...@unsatisfactorysoftware.co.uk>,
> Chris Young <chris.yo...@unsatisfactorysoftware.co.uk> wrote:
> > On Fri, 08 Mar 2013 16:25:07 GMT, John Rickman Iyonix wrote:
> 
> > > Mystery solved - I develop my web pages "offline" using relative
> > > reerences to files. NetSurf behaves differently in this "mode"
> > > with files and does not pick up the common favicon.
> 
> That's because you are using the filer. If you use WebJames to serve
> your files locally (http://localhost/) you will find that NetSurf
> finds favicon.ico in the root and uses it appropriately.
> 
> > > It behaves the same as you describe when accessing pages from the
> > > web server.
> 
> 'a' web server. :-)
> 
> > If you are working locally, the root will be the root of the
> > volume/drive your pages are stored on, which probably isn't the same
> > as the root directory of the files you are going to upload.  Hence
> > NetSurf won't find favicon.ico locally unless you give it additional
> > hints in HTML HEAD using relative paths.
> 
> Tried that but using the filer doesn't seem to work at all. Placing
> favicon.ico in the root of the disc seems to be ignored by browsers
> inc., NetSurf. (This isn't desired anyway unless you are a fan of
> clutter.)

Interesting.  I get the icon shown both in netsurf and other browsers
and in Netsurf both on a local disc and from an internet server.

Sometime I must have looked something up as I have this line in the
header of my index.html file:

<LINK REL="SHORTCUT ICON" HREF="favicon.ico" TYPE="image/x-icon">

All I can say now is that I wonder if this is relevant?

-- 
Tim Powys-Lybbe                                           t...@powys.org
             for a miscellany of bygones: http://powys.org/

Reply via email to