In article <[email protected]>, Martin Bazley
<[email protected]> wrote:
> The following bytes were arranged on 28 Aug 2011 by Tim Hill :

> > In article <[email protected]>, Richard Porter
> > <[email protected]> wrote:
> > > On 27 Aug 2011 Richard Torrens (lists) wrote:

> > > > Netsurf takes H REF="www.etc to refer to a external link.

> > > Firefox is correct because you might well have a subdirectory
> > > called www. On the other hand www.etc in an email message will
> > > ordinarily be an external link because a relative link is
> > > meaningless unless you happen to be discussing html.
> >
> > This is all true. I renamed some directories www_thingy_tld exactly
> > because a browser was wrongly assuming a RO  dir www/thingy/tld was
> > a relative link. 
    ^^^^^^^^^^
Oops, I meant 'an external'. Mea culpa.

> > It was a copy of a web site so naming it by its URL
> > made perfect sense. To me at the time, anyway.

> Surely a relative link is precisely what you want in that context?

_Exactly_

> You'd be in trouble if NetSurf decided it was an external link, as
> opposed to the name of the directory!

It did. At least I think it was an early NetSurf. May have been another.
Was a long time ago.

> Richard Torrens is also wrong - NetSurf, like Firefox, treats
> href="www.etc" as a relative link, as it should do.

Now.

>  This can cause
> problems when people wrongly assume that a link starting "www" without
> the "http" before it should be external - it's not, it's relative! I've
> seen this particular mistake in more web pages than I care to count. I
> have no idea why he thinks NetSurf and Firefox behave differently, but
> I assure you, they don't.

I think that the point is that at some time in the distant past some of
us do remember that a RISC OS browser (NetSurf was it?) did treat the
relative "www....." as if it had the external "http://"; prefix. I
remember because I had to change some local directory names to avoid
this. It wasn't imagined but it was ages ago.

To be clear: NetSurf r12640 currently in use here certainly DOES NOT have
this problem. The OP may need to upgrade.

T

-- 
Tim Hill
..............................................................
                                                www.timil.com


Reply via email to