Dimitri van Heesch

I don't understand why adding support for comments requires changes to example 055? The example without the `@page` command should also be valid I would expect.

@mnguyenpdftron without being able to reproduce the problem (since you only provided output and not a way to generated said output), it looks like your project uses a custom HTML...

@JasperCraeghs Please verify if the referenced commit fixes the problem for you.

@udaken I agree with Albert that the proposed logic is strange, and what about the other uses of `Portable::system()` that have `commandHasConsole` (implicitly) set to `true`? Should these also be...

@jothepro This is indeed an unfortunate limitation I did not foresee. Actually seems like a bug introduced in recent versions of chromium. In the past: ```css ::-webkit-scrollbar { all:unset; }...

@jothepro To avoid introducing yet another option, I'm thinking about adding the `::-webkit-scrollbar` stuff to `doxygen.css` only when no `HTML_EXTRA_STYLESHEET` has been specified. With the idea that you can always...

@jothepro Please verify if the referenced commit indeed solves the problem. Please do not close the issue, it will be done automatically when a new release is made available.

Looks like the main problem is that the member group documentation (i.e. the documentation associated with `@name`) is rendered twice, once for the namespace documentation and once more for the...

Indeed, the warning that was introduced is too simple/naive and does not take function pointers or function types into account. You can of course argue that a pointer or type...

I've limited the parameter check to real functions now. Could still be improved, but at least this should prevent the "false" warnings when `@param` is used on other types.