to netscape.public.mozilla.documentation and loudly proclaimed:
Phillip, I could /swear/ we went thro' this several months ago, with the conclusion that the appropriate RFC was not entirely clear as to whether ' ' should be escaped or not. That is, it /is/ escaping it properly; whether it /should/ be doing so is another matter.Brant Langer Gurganus wrote:How about: when someone has mistyped a link with spaces.I am trying to come up with a document for bug 74263 involving where Mozilla has intentionally deviated from the standards. If you know of where Mozilla has done this, please let me know. I know about <blink> and <marquee>. Please make sure your replies go to the netscape.public.mozilla.documentation list only. -- Brant Langer Gurganus Default QA Contact, Europe: West Mozilla Technology Evangelism
In Netscape Communicator if it came across such a link it would show an
error first in fine print abount the Apache Sever version then either a
400 error or 404 error. According to W3C standards this is correct
action.
In Mozilla and Netscape 7 they automatically insert %20 where the spaces
are located and thus allowing link to work. This is some what equivelent
to IE's action of self-healing a site which has missing tags.
It's not clear whether choking on it is appropriate behaviour.
And never, ever use NC as a benchmark. NC showed alt tooltips, too, after all.
And this is not at /all/ like IE's behaviour.
I suspect that the behaviour is allowed more on the basis of how files are at times named -- the way in which some software will name MP3s, for instance, is a case in point.
/b.
<snip />
--
Mozilla end-user questions should be directed to:
* snews://secnews.netscape.com:563/netscape.mozilla.user.general
* snews://secnews.netscape.com:563/netscape.mozilla.user.win32
* snews://secnews.netscape.com:563/netscape.mozilla.user.mac
* snews://secnews.netscape.com:563/netscape.mozilla.user.unix
Note that you need to have SSL enabled and the port set to 563.
