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 707278 - Grouping of results fail when using built-in javascript search
Grouping of results fail when using built-in javascript search
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.6-GIT
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-09-02 10:45 UTC by Suzumizaki-Kimitaka
Modified: 2016-12-29 18:45 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
fix grouping results of built-in javascript search (720 bytes, patch)
2013-09-02 10:45 UTC, Suzumizaki-Kimitaka 		none Details | Review
Self contained example to show this issue (and new patch) (456.51 KB, application/x-zip-compressed)
2013-09-24 10:08 UTC, Suzumizaki-Kimitaka 		  Details
New patch for 1.8.6+ (703 bytes, patch)
2013-12-26 12:03 UTC, Suzumizaki-Kimitaka 		none Details | Review

Description Suzumizaki-Kimitaka 2013-09-02 10:45:32 UTC 
Created attachment 253825 [details] [review]
fix grouping results of built-in javascript search

This patch fixes only 2 lines ;)

Consider using built-in javascript search. When some entries have common local name, doxygen sometimes fails grouping them.
Typical case is constructors. They have same local name but different arguments.

Ideal behavior seems to show only the common name at first, and when users click the name, grouped entries are shown.
But because of this bug, following bad behaviors are met (not always).

1) Both clickables, the header of common name and the links to each entries(not grouped) are shown.
2) Even clicking on the common name, nothing would happen.

Regards, 
Suzumizaki-Kimitata
Comment 1 Dimitri van Heesch 2013-09-16 20:21:48 UTC 
I don't really see a difference with or without the patch. Can you please attach a self-contained example where the difference is visible?
Comment 2 Suzumizaki-Kimitaka 2013-09-24 10:08:42 UTC 
Created attachment 255616 [details]
Self contained example to show this issue (and new patch)

I found more conditions should be met to represent this issue.
I made zip file that contains source and generated html pages.
Please read the *_patch/html/index.html for more detail.

Regards, 
Suzumizaki-Kimitata
Comment 3 Suzumizaki-Kimitaka 2013-12-26 12:03:09 UTC 
Created attachment 264901 [details] [review]
New patch for 1.8.6+

I made new patch to catch up with doxygen 1.8.6.
The old one included in the previous attachment(255616) is obsolete, but the sample included in the 255616 is alive.

Regards,
Suzumizaki-Kimitaka
Comment 4 Dimitri van Heesch 2016-12-18 14:00:06 UTC 
Confirmed. I'll include an updated version of the patch in the next github update.
Comment 5 Suzumizaki-Kimitaka 2016-12-20 03:54:24 UTC 
Thank you.
I haven't use Doxygen for years, but I believe this patch will make all you happy.

Regards,
Suzumizaki-Kimitaka
Comment 6 Dimitri van Heesch 2016-12-29 18:45:50 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.13. 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 (preferably in the form of a self-contained example).