I think of opening a New task for making the links to particular sections of the same article to scroll to that section of the article instead of opening a new page of the same article to display that section.

This doesn't seem to be the case with all the links. I recently tried to open the article on Lexical scoping which is actually a redirect link to the Lexical scope section of the the Scope article. It seems to work fine. I have attached screen shot of the section and the top of the article being displayed after I loaded the article using the redirect link.

Screen shot showing the section and text above it that has loaded

Screen shot showing the main section of article

I also find it weird that when I search for "Lexical scoping" in the search bar, I get the result as shown in the screen shot below:

Notice that message Redirected from Lexical scoping shown below the first result.

When I search for "Web 1.0" in the search bar, I get the result as shown in the below screen shot:

It's clear that there is no message about the redirection and although a redirect page exists for Web 1.0 it only shows Web 2.0 as the first result. That seems weird, doesn't it.

What could be the reason behind this ?

This bug may not be reproducable now after I edited the redirect link of "Web 1.0" to change it from

#REDIRECT [[Web 2.0#"Web 1.0"]]

to

#REDIRECT [[Web 2.0#Web 1.0]]

I did this after I changed that section's title from "Web 1.0" to Web 1.0.

I don't know why, but when you click that link I specified in the 3rd step now the app loads only the article and shows the main section instead of navigating to that section. The browser seems to be correctly navigating to that section though.

I also tried changing the redirection link to #REDIRECT [[Web_2.0#Web_1.0]] to test if works at least with that underscore but, it also had no effect. That edit has now been reverted by a person as unconstructive.

Why doesn't the app recognise that redirection link correctly ?

Anybody has any ideas regarding this weirdness ?

This points towards an issue in the backend content service that we use to fetch page contents. I created T148645 to account for this.

This example seems to be behaving properly in the current version of the app, for me (even though it's currently back to "Web 1.0" with the quote marks). I go directly to the correct section when I tap the 1.0 link, without any missing content that I notice.

However, on another page that instead uses the {{anchor}} template for the target, it does not work at all. It's not clear to me whether this is the same issue and caused by the backend content service one, or something different, so I'll open a new task. But this one is maybe resolved?

In T147836#3464153, @Ragesoss wrote:

This example seems to be behaving properly in the current version of the app, for me (even though it's currently back to "Web 1.0" with the quote marks). I go directly to the correct section when I tap the 1.0 link, without any missing content that I notice.

However, on another page that instead uses the {{anchor}} template for the target, it does not work at all. It's not clear to me whether this is the same issue and caused by the backend content service one, or something different, so I'll open a new task. But this one is maybe resolved?

This seemed to be working for you as I had changed that into an internal link in April 2017.

Anyways, this issue seems to be a little worser nowadays. T184824: Redirect link to a specific section of a page just loads that page