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 666986 - filter options and search results included twice for class files in namespaces
filter options and search results included twice for class files in namespaces
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.6.1
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-12-29 13:44 UTC by haferfrost
Modified: 2012-02-25 15:37 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
doxygen with default options produces nonvalidating structfoo_1_1A.html (116 bytes, text/x-c++src)
2011-12-29 13:44 UTC, haferfrost 		Details

Description haferfrost 2011-12-29 13:44:02 UTC 
Created attachment 204316 [details]
doxygen with default options produces nonvalidating structfoo_1_1A.html

Steps to reproduce:

mkdir test
cd test
cp <attachment-to-this-bug> test.cpp
doxygen -g
doxygen

less html/structfoo_1_1A.html

The following parts occur twice, once before and once after the <div class="contents">


<!-- window showing the filter options -->
<div id="MSearchSelectWindow"
...
<!-- iframe showing the search results (closed by default) -->
<div id="MSearchResultsWindow">
...



This causes a validation error due to the duplicate id attributes.

The error only seems to affect classes in namespaces. If I remove the namespace the error does not occur.

Tested with doxygen-1.7.6.1 (self-compiled from the tar.gz) on Ubuntu Lucid.
Comment 1 Dimitri van Heesch 2011-12-29 15:15:26 UTC 
Confirmed. Should be fixed in the next subversion update.
Comment 2 Dimitri van Heesch 2012-02-25 15:37:16 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.0. 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.