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 658218 - Html stylesheet link incorrect
Html stylesheet link incorrect
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.5.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks: 673984
 
 
Reported: 2011-09-05 06:22 UTC by Martin Gunia
Modified: 2012-07-09 17:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Martin Gunia 2011-09-05 06:22:26 UTC 
Hello,

the path for the linked CSS stylesheet in HTML pages seems to be taken directly from the Doxyfile's HTML_STYLESHEET parameter, instead of pointing to the local copy (where index.html is generated) as with Doxygen 1.7.4. 


For the setting of HTML_STYLESHEET = ./doc/doxygen.html

Doxygen 1.7.5.1 generates:

<link href="tabs.css" rel="stylesheet" type="text/css"/>
<link href="./doc/doxygen.css" rel="stylesheet" type="text/css" />

Doxygen 1.7.4 generates:

<link href="tabs.css" rel="stylesheet" type="text/css"/>
<link href="doxygen.css" rel="stylesheet" type="text/css" />


This results in the stylesheet not being found by browser. I haven't found any note of change in the stylesheet behavior in ChangeLog so assume this is a bug. I can upload sample code and Doxyfile, if needed.
Comment 1 Martin Gunia 2011-09-05 06:24:29 UTC 
This *may* be related to the bug 657704 (https://bugzilla.gnome.org/show_bug.cgi?id=657704).
Comment 2 Ivan Stankovic 2011-11-18 14:06:05 UTC 
I've also recently ran into this bug. It's really annoying and
there does not seem to be a workaround.
Comment 3 Dimitri van Heesch 2012-07-08 15:01:08 UTC 
Hi Ivan,

Which version of doxygen are you using?
Comment 4 Ivan Stankovic 2012-07-09 10:33:13 UTC 
Hi,

I've recently upgraded to 1.8.1.1 and the problem seems to have
been fixed.
Comment 5 Dimitri van Heesch 2012-07-09 17:48:15 UTC 
Ah good to hear.