https://bugzilla.wikimedia.org/show_bug.cgi?id=24918
--- Comment #9 from Aryeh Gregor <simetrical+wikib...@gmail.com> 2010-08-27
17:22:32 UTC ---
(In reply to comment #8)
> But unencoded "[" and "]" are
> clearly non-compliant. RFC 3987 says "... square bracket characters ... MUST
> NOT be converted" and then RFC 3986 says "A host identified by an Internet
> Protocol literal address, version 6 [RFC3513] or later, is distinguished by
> enclosing the IP literal within square brackets ("[" and "]"). This is the
> only place where square bracket characters are allowed in the URI syntax."
Hmm. We could strip those too, but it seems silly if all browsers accept them.
If the spec requires something that not all browsers support, and prohibits
something equivalent that all browsers do support, the spec is broken.
> Separate, but related. There is apparently no way to write links to sections
> with "[" and "]" in the title as external links (this includes permalinks)
> without getting them percent-encoded (more than that, it's hard to write them
> at all, as they clash with wiki markup).
The sensible thing would be to urldecode() anchors automatically in external
links, if that's what it takes for IE to accept them . . . if that's necessary
for the links to actually work but specs prohibit it, the specs are wrong. But
that's a separate issue from a development perspective, as I said, although
conceputally related.
> Other than that, I'm not sure if stripping the most problematic characters is
> the right approach at all. It doesn't solve all compatibility issues. I've
> just
> noticed the following: Paste http://example.com/#< into Firefox' address bar.
> Copy from there and paste into an arbitrary text editor. You'll get
> http://example.com/#%3C (tested in a current Firefox 4.0 nightly), which
> doesn't work in IE. This happens with some funny ASCII characters like "<" and
> ">", but also - and that's far worse - non-ASCII characters that occur in
> natural language.
>
> So Firefox users will create links that don't work in IE as long as IE doesn't
> understand percent encoding.
This seems like a minor enough failure. At worst, the very small number of
people who this happens to won't make it to the right section. Not the end of
the world.
I've reported the issue to Microsoft, after verifying that it still exists in
IE9PP4:
https://connect.microsoft.com/IE/feedback/details/590087/percent-encoding-fragments-hashes-anchors-does-not-work
(A [free] Microsoft Live account is needed to view.)
--
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
