Link-Parser

[QDP2012]

Good morning Forum Admins,

As experienced most-recently with Chauffer6's post in another thread, the RR Forum-engine's link-parser seems not to properly parse links which contain a space, when the space is in an HTML "Name" tag, like those used to navigate up and down within single web-page.

The original link Chauffer6 provided, in the other thread, was...

http://marksscanners.com/BCT15X/bct15x.shtml#group keys

...but the Forums-engine parsed it as...

http://marksscanners.com/BCT15X/bct15x.shtml#group%20keys

I know that %20 substitution is required for spaces in the primary part of the URL.

But, is there a way to make the link-parser properly handle links in situations like this, so that it does not substitute the %20 for spaces that occur after the # character?

Thanks for your time and consideration.

Respectfully,

 

[QDP2012]

(This reply is posted here in response to this post, to avoid an OT post in the other thread.)

IE, Firefox and Chrome all took me directly to the point in the document referenced when I clicked on the link. Perhaps you don't have the most current version of the browser?

True. Not the most current browser, because not the most current OS.

Testing on this end shows:

• does not parse correctly on IE 8 on Windows XP
• does not parse correctly on IE 9 on Windows 7x64
• does parse correctly on FF 15 on Windows 7x64

When the link is not parsed correctly, the page loads but stays at the top of the page instead of jumping down to the specified "Name" anchor tag. Based upon the OP's description in their reply to Chauffeur6, I (maybe incorrectly) assumed this behavior might be what the OP experienced. I have bumped into this issue several times, but can get around the issue with a copy-paste of the original link, or by replacing %20 with a real space.

Thanks,

.

 

[WayneH]

I don't know what we can do on our end. I just tried it and it works fine for me.

 

[QDP2012]

Thanks

Thank you sir for checking. It seems like the issue is probably more on my end than on yours anyway -- with respect to browser-versions, OS-versions, etc.

Thanks again,