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

Grouping of results fail when using built-in javascript search (Origin: bugzilla #707278) #5280

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2013-09-02 10:45:32 +0000, Suzumizaki-Kimitaka wrote:

Created attachment 253825
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.


On 2013-09-16 20:21:48 +0000, Dimitri van Heesch wrote:

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?

On 2013-09-24 10:08:42 +0000, Suzumizaki-Kimitaka wrote:

Created attachment 255616
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.


On 2013-12-26 12:03:09 +0000, Suzumizaki-Kimitaka wrote:

Created attachment 264901
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.


On 2016-12-18 14:00:06 +0000, Dimitri van Heesch wrote:

Confirmed. I'll include an updated version of the patch in the next github update.

On 2016-12-20 03:54:24 +0000, Suzumizaki-Kimitaka wrote:

Thank you.
I haven't use Doxygen for years, but I believe this patch will make all you happy.


On 2016-12-29 18:45:50 +0000, Dimitri van Heesch wrote:

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).

@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