After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 737830 - Invalid element name in footer part when GENERATE_TREEVIEW specified
Invalid element name in footer part when GENERATE_TREEVIEW specified
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.8
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-10-03 09:18 UTC by James Kanze
Modified: 2015-01-06 11:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
gzipped tar file which displays the error (3.28 KB, application/gzip)
2014-10-03 09:18 UTC, James Kanze
Details

Description James Kanze 2014-10-03 09:18:00 UTC
Created attachment 287650 [details]
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.
Comment 1 Dimitri van Heesch 2014-12-23 13:57:40 UTC
Hi James,

The file you attached seem to be corrupted. Can you attach a corrected version?
Comment 2 Dimitri van Heesch 2014-12-23 14:03:35 UTC
Nevermind, I was able to reproduce the issue from the description given.

Should be fixed in the next GIT update.
Comment 3 Dimitri van Heesch 2014-12-25 16:03:42 UTC
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).
Comment 4 James Kanze 2015-01-06 11:54:24 UTC
Just checked; it's working now.  Thanks.