Doxygen cannot resolve link to HTML anchor page

[lcarlier]

Describe the bug
Doxygen cannot resolve link to HTML anchor page in the same document.

Expected behavior
The link should be generated

Screenshots
/home/lcarlier/Projects/bugDoxygen/README.md:6: warning: unable to resolve reference to 'user-content-as' for \ref command
/home/lcarlier/Projects/bugDoxygen/README.md:6: warning: unable to resolve reference to 'user-content-as' for \ref command

To Reproduce
Untar the attached tar ball and execute doxygen using the contained doxyfile.
bugDoxygen.tar.gz

Version
This is a regression.
The patch introducing the problem is 3a4db85
The parent version is working fine.

Stack trace
NA

Additional context
I was trying to find a fix but it isn't clear to me what could be the right solution. I thought of adding the section manually via SectionManager::instance().add but the name of the output HTML isn't known inside markdown.cpp so I'm not sure whether that would be the right thing to do.

Looking at the updated documentation, it seems that some inconsistencies have been introduced.

This is the patch I was trying but it isn't working

diff --git a/src/markdown.cpp b/src/markdown.cpp
index bacefc85..f8ddeeb5 100644
--- a/src/markdown.cpp
+++ b/src/markdown.cpp
@@ -52,6 +52,7 @@
 #include "regex.h"
 #include "fileinfo.h"
 #include "utf8.h"
+#include "pagedef.h"
 
 enum class ExplicitPageResult
 {
@@ -1225,7 +1226,8 @@ int Markdown::processLink(const char *data,int,int size)
         m_out.addStr(" \"");
         m_out.addStr(substitute(content.simplifyWhiteSpace(),"\"","""));
         m_out.addStr("\"");
-
+        SectionManager::instance().add(&link.data()[1],
+                                       m_fileName,-1,title,SectionType::Anchor,0,"");
       }
       else
       {

[albert-github]

I see a second one missing as well, i.e. with an explicit link:

* [A second section](#user-content-as)

though both have the same background.
The referenced git ID is for: "issue #8956 Section links in markdown mainpage not working" i.e. pull request #8961

[albert-github]

I tried the "patch" but this gives some new problems when we have the file README.md as:

# Welcome to Bug readme
## <a name="user-content-as"></a> Problem with the link
The link in the table of contect isn't correctly generated and a warning appears saying it can't resolve \\ref for user-content-as

I would expect the link to be correct generated

## Table of content
* [A section][as]
* [A second section](#user-content-as)

[as]: #user-content-as


## Header 1

## Header 2 {#label_header_2}

[Link to header 1](#header-1)

[Link to header 2](#label_header_2)

we get the warning:

.../README.md:16: warning: multiple use of section label 'label_header_2' while adding section, (first occurrence: .../README.md)

Furthermore [Link to header 1](#header-1) will show as a link and this is incorrect as discussed at #8956

[lcarlier]

The patch isn't working indeed. It is a failed attempt.

I'm not sure this is the right solution though. We would need a way to know whether the #link corresponds to a class or an internal page link.

[albert-github]

Indeed, I'm looking into the problem (might take a little while though).

[lcarlier]

I just though if this quick and dirty fix...

#9201

[albert-github]

#9200 (comment) my comment with the proposed pull request.

[albert-github]

I've just pushed a proposed patch, pull request #9204

[lcarlier]

I'll test this probably Thursday or Friday