- From: Erik van der Poel <erikv@google.com>
- Date: Sat, 26 Sep 2009 08:19:14 -0700
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- Cc: PUBLIC-IRI@w3.org
MSIE, Firefox and Chrome all allow # in the fragment, and they scroll
down to the location of an anchor with such a name.
It is unfortunate that XML Schema uses ##other in places where
resource identifiers are expected, but XML Schema and HTML are two
different contexts, so maybe it doesn't matter so much.
Would you care to elaborate on your comment about people as implementations?
Erik
>>>>> I seem to remember something to the effect that some implementations
>>>>> parsed URIs from the back to chop off the fragment part.
>>>>
>>>>Ugh. Just say No to such implementations. Always parse forward.
>>>
>>> People attempting to chop off the fragment identifier to pass only
>>> the address along are rather unlikely to follow your advice.
>>
>>Do you know of implementations that parse backwards from the end to
>>find the beginning of the fragment part?
>
> Examples are easy to find using Google's code search for a term like
> "url" and a pattern like rfind('#') or lastIndexOf('#'); that gives
> for example the com.google.thingbrowser.api.UrlUtilities package with
> its splitUrlAndFragment method that appears to do just that (quite
> possibly in that particular case it does not matter, but there are
> many other hits). There are also specifications that rely on "#" being
> prohibited in the fragment identifier, e.g. XML Schema uses strings
> like "##other" in places where resource identifiers are expected.
> But again, people are the relevant "implementations" here.
> --
> Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
> Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
>
Received on Saturday, 26 September 2009 15:19:53 UTC