You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since 1.8.12 there is new main menu. It completely relies on Javascript which makes navigation unavailable for search engines and anyone without JS enabled. Also, it does not highlight the current page.
There is no good reason to use JS to render essential navigation.
Please return the old menu.
On 2017-01-10 20:13:59 +0000, Dimitri van Heesch wrote:
I'll reintroduce the old style navigation in the next git update.
To enable it set HTML_DYNAMIC_MENUS to NO in the config file.
I also stumbled about those new menus (using 1.8.13). But on my part I get a 'ReferenceError' inside the Firefox JavaScript Konsole (and also IE) wrt. to
<script type="text/javascript">
$(function() {
initMenu('',false,false,'search.php','Search');
});
inside 'index.html'. It tells me
18:40:42.509 ReferenceError: $ is not defined 1 index.html:11:1
http://.../Doxygen/index.html:11:1
I do not get any menus, too. I'm not JS expert: is this $( ... ) really a valid JavaScript expression?
On 2017-01-17 18:14:39 +0000, Josef Kufner wrote:
$() is just a function call - see jQuery, which is likely missing.
On 2017-08-14 12:48:02 +0000, Erwan Y wrote:
on the version 1.8.12 and 1.8.13 , when i am generating a chm file
(Compiled HTML file)
There is an issue
Line: 26
Error: The value of the property '$' is null or undefined, not a Function object
Search.html and search.php is not present in the generated directory
i have no Menu too.
On 2017-08-14 12:53:05 +0000, Erwan Y wrote:
on the version 1.7.X, the menu is correct on chm mode and html mode
Created attachment 357551
error screenshot after opening chm file generated by Doxygen 1.8.13
On 2017-12-25 18:44:01 +0000, Dimitri van Heesch wrote:
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.14. 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).
The text was updated successfully, but these errors were encountered:
status RESOLVED severity blocker in component general for ---
Reported in version 1.8.12 on platform Other
Assigned to: Dimitri van Heesch
Original attachment names and IDs:
On 2017-01-07 00:58:54 +0000, Josef Kufner wrote:
On 2017-01-10 20:13:59 +0000, Dimitri van Heesch wrote:
On 2017-01-10 20:49:54 +0000, Josef Kufner wrote:
On 2017-01-17 17:47:18 +0000, heiko.nardmann@itechnical.de wrote:
On 2017-01-17 18:14:39 +0000, Josef Kufner wrote:
On 2017-08-14 12:48:02 +0000, Erwan Y wrote:
On 2017-08-14 12:53:05 +0000, Erwan Y wrote:
On 2017-08-14 12:54:16 +0000, Erwan Y wrote:
On 2017-12-25 18:44:01 +0000, Dimitri van Heesch wrote:
The text was updated successfully, but these errors were encountered: