Re: Extended URL for frames
| Daniel W. Connolly <email@example.com> writes:
| > Hmmm... I'm pretty sure I've seen implementations that scan
| > from the right for the first #, and consider that to be the
| > split between the URL and the fragment identifier.
| This is the first step in the parsing algorithm described in RFC
| "Relative Uniform Resource Locators" (http://www.w3.org/pub/WWW/
How can this be, if the same spec states that the fragment starts at
the FIRST # character ... I would say someone wasn't thinking... or
was assuming that all other # characters would be escaped... bad
thinking unless they explicitly state this in the spec...