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 708446 - Deprecated list breaks HTML tree with xhtml extension
Deprecated list breaks HTML tree with xhtml extension
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.5
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-09-20 11:19 UTC by Stuart Mills
Modified: 2013-12-24 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example demonstrating problem with deprecated list with xhtml file extension (25.35 KB, application/x-zip-compressed)
2013-09-20 11:19 UTC, Stuart Mills 		Details

Description Stuart Mills 2013-09-20 11:19:56 UTC 
Created attachment 255380 [details]
Example demonstrating problem with deprecated list with xhtml file extension

We use .xhtml as the file extension for HTML output in order to support svgs in Internet Explorer.  However, when our documentation is built with release 1.8.5, the tree is not displayed, and the panel on the left is blank.  1.8.4 didn't exhibit this behaviour.

Further investigation has shown that this seems to be caused by including the deprecated list.  Changing back to .html file extensions also solves the problem.

The behaviour is consistent in both Chrome and IE.

The attached zip file includes both a C source file and a Doxygen configuration file demonstrating the behaviour.
Comment 1 Dimitri van Heesch 2013-09-21 12:48:14 UTC 
Confirmed, problem was due to the use of   in navtree.js which isn't defined in XHTML. I now replaced it with  . Should be corrected in the next GIT update.
Comment 2 Stuart Mills 2013-09-24 15:01:39 UTC 
Works perfectly for us now.  Thanks for the speedy response.
Comment 3 Dimitri van Heesch 2013-12-24 18:59:56 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. 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).