Re: a bad idea (fwd)

Walter Ian Kaye (
Tue, 16 Jul 1996 17:31:09 -0700

Message-Id: <v03007805ae11e30a277a@[]>
In-Reply-To: <>
Date: Tue, 16 Jul 1996 17:31:09 -0700
From: Walter Ian Kaye <>
Subject: Re: a bad idea (fwd)

At 2:25p -0700 07/15/96, Marcus E. Hennecke wrote:
>On Mon, 15 Jul 1996 13:28:22 -0700, "Marc Salomon" <> wrote:
>> Marcus E. Hennecke <> wrote:
>> |It would break Netscape. It simply takes everything in the quotes to be
>> |the URL, including spaces. If you try:
>> |<a href="">Follow this link</a>
>> It didn't used to break Navigator, at least when I tested it last year.
>I guess the reason they do it that way now is so they can do:
><a href=" subject">Mail me</a>
>which of course breaks every other browser, including older versions of
>> If what you say is true, that means that Navigator's interpretation of a
>>URI is
>> noncompliant per RFC 1738, Section 2.2, and this convention would expose an
>> already broken implementation.
>Did Netscape ever give a s**t about standards? However, AFAIK, spaces are
>not allowed inside URLs, so if one appears inside a URL attribute, I am
>not sure what is more appropriate: encode the space (%20) or truncate the
>URL at that point. Netscape appears to encode spaces and I would think
>this is within its rights.

This is why I suggested using the generic CONTENT attribute of a META tag.
Since it is not a "URI field", it can be parsed in whatever manner is
appropriate for the NAMEd content (in this case, a space-delimited list of
URIs). Of course there is the added benefit of leaving the HTML in the
body much less cluttered -- I want tags in the body to take up as *little*
room as possible, to facilitate easy manual editing of body *content*.

    Walter Ian Kaye <>     Programmer - Excel, AppleScript,
          Mountain View, CA                         ProTERM, FoxPro, HTML     Musician - Guitarist, Songwriter