Mark Anderson wrote:
>..
>
> But this, of course, is a moot point and ancient history (hindsight is,
> after all, 20/20). And with regards to the topic at hand, since it's
> been shown that older browsers don't even show a differentiation between
> the wrong URLs and the syntactically correct ones, I think we should go
> with Duane's interpretation but have some way to flag it (just accepting
> an incorrect URL as correct still strikes me as wrong) as incorrect.
>
> Thankfully, XHTML can get off on the right foot and fix the current
> problems somewhere off in the future. (This bleeds over into that
> n.p.m.editor thread on making Composer separate structure from content.
> :) )
Going way back to my original whining that started this thread... I did
not intend for this to degrade into a discussion of this one particular
bug, which I really don't think is extremely widespread. I was trying to
point out that in general I think that making the solution to bad links
as "contact the web site administrator", to be a poor solution. Yes they
probably should be contacted, but I think that Mozilla also needs to
realize that there are bad links out there, and that it needs to deal
with them in a reasonable way.
And it is not just "ordinary people". For example, this interesting
exchange on bugzilla about a bad link on
http://www.w3.org/People/all
http://bugzilla.mozilla.org/show_bug.cgi?id=66272
------- Additional Comments From Daniel Glazman 2001-01-23 07:44 -------
Good catch. The HTML specs says that comparisons between fragment
identifiers
[p.18] and anchor names must be done by exact (case-sensitive) match, but
identifiers but must obviously be unescaped first... So W3C has illegal
markup on his page.
How could I suspect that from W3C ?-)))
Closing bug as invalid.
------- Additional Comments From Daniel Glazman 2001-01-23 07:49 -------
evang mail sent to [EMAIL PROTECTED]
And here is another:
http://bugzilla.mozilla.org/show_bug.cgi?id=50158
------- Additional Comments From Frank Tang 2000-10-23 14:11 -------
jaimejr, this is not a client bug but a content problem. Please help to
find AOL webmaster to fix this. Thanks.
--
My real email is akamail.com@dclark (or something like that).
