New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid element name in footer part when GENERATE_TREEVIEW specified (Origin: bugzilla #737830) #5647

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.8 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2014-10-03 09:18:00 +0000, James Kanze wrote:

Created attachment 287650
gzipped tar file which displays the error

When the input file contains an explicit template specialization, and GENERATE_TREEVIEW is specified, the HTML generated for the specialization contains an invalid element name in the footer part; the class name in one of the elements is literally "Test< char const* >", and of course, "< char const* >" looks like an element to the browser. (The error is in navigation information in the footer, which won't be displayed.)

How this is handles depends on the browser: IE goes ahead and displays the page normally; Firefox just displays an "XML Parsing Error", and nothing else, and Chrome displays the page correctly, with a box with an error message at the top.

I've attached a gzipped tar file with the Doxygen configuration file (.dox) and a very simplified version of a header file (.hh) which triggers the error.

On 2014-12-23 13:57:40 +0000, Dimitri van Heesch wrote:

Hi James,

The file you attached seem to be corrupted. Can you attach a corrected version?

On 2014-12-23 14:03:35 +0000, Dimitri van Heesch wrote:

Nevermind, I was able to reproduce the issue from the description given.

Should be fixed in the next GIT update.

On 2014-12-25 16:03:42 +0000, Dimitri van Heesch wrote:

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

On 2015-01-06 11:54:24 +0000, James Kanze wrote:

Just checked; it's working now. Thanks.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment