\ref command does not respect "text" field for template classes in Doxygen 1.10.0 - trunk

[scott-zhong]

Describe the bug
\ref command does not respect "text" field for template classes.

/**
 * Base
 */
template <class T>
class Base;

/**
 * \ref Base "Base<int>"
 */
class Test {
};

Screenshots
Doxygen 1.9.8:

Doxygen 1.10.0 - trunk (38ee114)

To Reproduce
testcase.zip

Expected behavior
\ref command should use the "text" field when template classes are referenced, similar to behavior for non-template classes.

[albert-github]

It looks like the problem is introduced in:

Commit: 351dba64b602b2334f3d7400af1088c1be62aa99 [351dba6]
Date: Sunday, December 17, 2023 7:52:34 PM

issue #10475 doxygen does not correctly render link content in MarkDown file

and more precise due to the rule (in doctokenizer.l):

<St_Ref2>{HTMLTAG}     { /* html tag */
                         lineCount(yytext,yyleng);
                         handleHtmlTag(yyscanner,yytext);
                         return TK_HTMLTAG;
                       }

Here it was necessary as the code to be rendered was (a.o.):

(line 9) This is some text with a link to [`doc/OTHER.md` file](doc/OTHER.md) using MarkDown link/reference notation.

which resulted after markdown processing in:

(line 9) This is some text with a link to @ref ".../issue_10475/doxygen-markdown-linking-problem/doc/OTHER.md" "<tt>doc/OTHER.md</tt> file" using MarkDown link/reference notation.

which resulted in the fact that (here) <tt> and </tt> were not rendered, due to the general definition of the HTML_TAG it also meant that non HTML_TAGs (like here <int>) were not rendered anymore.

@doxygen an idea?

[doxygen]

@albert-github Maybe a good heuristic is to only interpret an <X> tag as an HTML tag if there is also a matching </X> in the same reference text. Then Foo<tt> is left unprocessed and <tt>Foo</tt> is a Foo with typewriter markup.

[albert-github]

@doxygen
Indeed probably the only way though special care has to be taken with the odd ones out HTML tags <br>, <hr> ...
(looks like to be area, base, br, col, embed, hr, img, input, link, meta, source, track, wbr see https://html.spec.whatwg.org/#void-elements)
Interesting stack overflow question with a number of references in this respect: https://stackoverflow.com/questions/1946426/html-5-is-it-br-br-or-br

[doxygen]

@scott-zhong Please verify if the referenced commit fixes the problem for you. Do not close the issue, this will be done automatically when the next official release becomes available.

@albert-github I've made the allowed HTML tags in @ref more strict, the same was already done in paragraph context. Now one can also write:

\ref Base "See <tt>Base<int></tt> for more"

I think it's easy enough to explain and understand that a supported HTML tag cannot be used as a template argument as well.

[scott-zhong]

@doxygen @albert-github I have verified the fix. Thank you!!!

[doxygen]

This issue was previously marked 'fixed but not released',
which means it should be fixed in doxygen version 1.12.0.
Please verify if this is indeed the case. Reopen the
issue if you think it is not fixed and please include any additional information
that you think can be relevant (preferably in the form of a self-contained example).