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

custom CSS is missing (Origin: bugzilla #646319) #4220

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.7.4 on platform Other
Assigned to: Dimitri van Heesch

On 2011-03-31 10:46:29 +0000, Anton wrote:

Generated by "doxygen -w html" custom header does not include CSS given by

Generated by version 1.7.4 HTML header contains following line for CSS file inclusion:

but in version 1.7.3 it looks like:

P.S. Thanks for your work! doxygen is very nice but a little buggy :)

On 2011-03-31 11:02:08 +0000, Anton wrote:

Custom CSS file is copied normally into documentation directory. Problem only with link from HTML header

On 2012-02-10 03:33:54 +0000, Florian wrote:

This bug report is pretty hard to understand. I'll add a different description:

If HTML_STYLESHEET is an absolute path, it is copied verbatim into the generated HTML files. For instance, if we specify "HTML_STYLESHEET = /path/to/my/css/file" all HTML files then contain the header:

On 2012-02-11 22:54:43 +0000, Dimitri van Heesch wrote:

Thanks for the clarification. Problem should be fixed in the next subversion update.

On 2012-02-16 19:04:29 +0000, Dimitri van Heesch wrote:

*** Bug 670063 has been marked as a duplicate of this bug. ***

On 2012-02-25 15:37:20 +0000, Dimitri van Heesch wrote:

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.

@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