There is a general lacking of support for anchor and query params in links.

Concrete item: the redirectto parameter does not understand Web.Topic#Anchor syntax.

Overall, anchor syntax is largely not supported. It should not be difficult to add anchors and query parameters to a topic notation. The question is largely: where to add it?

Render.pm has the subroutine _handleWikiWord. But this is not used by Foswiki.pm code. Instead it uses normalizeWebTopicName a lot. With a small change that function could also return anchor and params:

-- CrawfordCurrie - 18 Mar 2009
Confirmed. However normalizeWebTopicName is not the place to add it; it relates to a topic name, not a general index, and is used in places where it would be quite inappropriate to do that.

Instead the params and anchor should be taken off only where it is appropriate to do so i.e. when parsing the target of a square bracket link, and when parsing a small subset of parameters such as redirectto. By all means provide a new function that fulfils the dual role of parsing off the args and normalizing the topic name, but don't muck with the existing normalizeWebTopicName function.

This was set "Waiting for release", but actually no checkins have been done.

Pending for a unit test.

Plus, I first regarded this as an enhancement, but it is a bug. For example with SendEmailPlugin after pressing submit, the redirect does not link to the feedback anchor with a possible error message. If that message is not in first view, it looks like the operation was succesful, while actually it failed. There must be a lot of other applications that rely on anchors that are now failing.

It was closed because the bug was fixed and a release with the fix was released 1.0.9

This also means that the item should remain closed and a new bug raised if there is more related work. Otherwise people get confused when they click on the fixed bug list in the release notes and find a non closed bug.

And we get confused when we cannot identify in which release a bug is fixed.

And last we end up with same bug item in several releases.

Open a bug related to the unit tests which can be closed when fixed as unit tests are not part of the released product.