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 666124 - Navigation pane blank in IE8 when HTML is served via Web server
Navigation pane blank in IE8 when HTML is served via Web server
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.6
Other Windows
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-12-13 20:35 UTC by Gail
Modified: 2012-02-25 15:37 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
doxyfile used to build the document in question (75.21 KB, text/plain)
2011-12-13 20:36 UTC, Gail
Details
Requested ZIP (169.06 KB, application/x-zip-compressed)
2011-12-15 22:05 UTC, Gail
Details
part 2 includes header files (1.90 KB, application/x-zip-compressed)
2011-12-15 22:28 UTC, Gail
Details

Description Gail 2011-12-13 20:35:19 UTC
HTML content that functions normally on the local drive malfunctions when docs are delivered to the user in IE8 via a Web server. Same docs opened in Firefox 8 function normally.

In IE8 on Windows 7, for docs served via a Web server, the navigation pane in the HTML doc appears blank. Same doc does not have this issue when opened on the local drive in IE8, nor does it have this issue when opened in Firefox 8 delivered via a Web server.

In IE8 the navigation pane flashes whenever you click a navigation button, so you can see that it is there, but the contents in the pane disappear almost immediately and cannot be clicked on.

Attaching doxyfile used.
Comment 1 Gail 2011-12-13 20:36:04 UTC
Created attachment 203387 [details]
doxyfile used to build the document in question
Comment 2 Dimitri van Heesch 2011-12-13 20:51:18 UTC
Can you please attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?
Comment 3 Gail 2011-12-15 22:05:59 UTC
Created attachment 203611 [details]
Requested ZIP

Requested files
Comment 4 Gail 2011-12-15 22:06:35 UTC
Attaching requested zip file; also includes the output in /html subdirectory. After extracting, you can test /html/index.html on local drive in IE8/Firefox, then test same output delivered via webserver. The IE8 navigation pane content disappears from webserver.
Comment 5 Gail 2011-12-15 22:28:13 UTC
Created attachment 203612 [details]
part 2 includes header files

Forgot to include the .H files.
Comment 6 Gail 2012-01-24 20:23:24 UTC
When will this be confirmed? It takes very little to place the /html subdirectory on a webserver and test whether the navigation pane appears. Thanks.
Comment 7 Dimitri van Heesch 2012-01-24 21:30:36 UTC
Which webserver are you using? Does the browser produce any errors in case it is not working?
Comment 8 Gail 2012-01-24 21:47:09 UTC
we are IIS running 6.0 on Windows 2003 server for our intranet.
Comment 9 Dimitri van Heesch 2012-01-28 10:34:28 UTC
I can reproduce what you see. When I select the address bar and press enter however, the navigation pane appear (and stays there even when navigating to other pages).

I still have no clue why this makes a difference, or how to debug/work around this IE8 "feature".
Comment 10 Dimitri van Heesch 2012-01-28 11:45:40 UTC
I think I have found the problem. 

To test it can you replace getScript() in navtree.js by

function getScript(scriptName,func,show)
{
  var head = document.getElementsByTagName("head")[0];
  var script = document.createElement('script');
  script.id = scriptName;
  script.type = 'text/javascript';
  script.onload = func;
  script.src = scriptName+'.js';
  script.onreadystatechange = function() {
    if (script.readyState=='complete' || script.readyState=='loaded') {
      func(); if (show) showRoot();
    }
  };
  head.appendChild(script);
}

and let me know if that fixes the problem?
Comment 11 Gail 2012-01-31 22:04:10 UTC
This fixes the issue. Thank you very much!
Comment 12 Dimitri van Heesch 2012-02-25 15:37:36 UTC
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.