On Fri, 28 Jul 2000, Dave Jenkins wrote:
Then you are wrong. :) You need to have amp; in there, so that the
browser can turn it back from amp; to before sending the URL back
up to your server (or whichever server comes along).
Are you really positive about this?
unlurk
I had
To be honest, I have always used plain ampersands in URLs embedded in my
pages, and thus far I have never encountered any problems.
But maybe I've just been lucky... ;-)
me too
Gerald
Michael Hanisch [EMAIL PROTECTED] writes:
On Fri, 28 Jul 2000, Dave Jenkins wrote:
Then you are wrong. :) You need to have amp; in there, so that the
browser can turn it back from amp; to before sending the URL back
up to your server (or whichever server comes along).
Are
From: Michael Hanisch [EMAIL PROTECTED]
Date: 2000-07-28 06:48:14 -0400
Are you really positive about this?
Randal is 100% correct.
AFAIK (and I just looked it up in the HTML 3.2 spec :-) the A tag is
defined as follows:
(quoted from http://www.w3.org/TR/REC-html32#sgmldecl)
So the
At 13:28 28/07/2000 +0200, Michael Hanisch wrote:
To be honest, I have always used plain ampersands in URLs embedded in my
pages, and thus far I have never encountered any problems.
But maybe I've just been lucky... ;-)
Forget about all those mindboggling HTML questions ! Use XHTML, there amp;
On 7/28/00 12:54 PM, Mark Doyle wrote:
We deliberately chose to use URL's with a series of '/' delimited fields
rather then using '? ... ' style URL's precisely because most people
don't know they have to escape the ampersands and we didn't want to risk
people's links breaking in the
On Fri, 28 Jul 2000, Michael Hanisch wrote:
I really believe my thoughts outlined in my original post are correct -
but right now I am starting to worry...
Personally I would attribute the described problem to a bug in IE4 - even
if it parses the URI for entities, it shouldn't find a "sect;"
On Fri, 28 Jul 2000, brian d foy wrote:
On Fri, 28 Jul 2000, Michael Hanisch wrote:
Personally I would attribute the described problem to a bug in IE4 - even
if it parses the URI for entities, it shouldn't find a "sect;" since the
Alan Flavell has an excellent article on this problem,
