Bug 755293 – Tree view pane overlaps with content tabs

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 755293 - Tree view pane overlaps with content tabs


Summary:	Tree view pane overlaps with content tabs


Status:	RESOLVED FIXED

Product:	doxygen
Classification:	Other
Component:	general
Version:	1.8.7
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Dimitri van Heesch
QA Contact:	Dimitri van Heesch

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2015-09-20 07:00 UTC by Slava Risenberg
Modified:	2015-12-30 10:19 UTC

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Treeview pane overaps with content tabs (87.39 KB, image/png) 2015-09-20 07:00 UTC, Slava Risenberg		Details
Proposed fix (586 bytes, patch) 2015-09-20 07:04 UTC, Slava Risenberg	none	Details \| Review

Description Slava Risenberg 2015-09-20 07:00:51 UTC

Created attachment 311690 [details]
Treeview pane overaps with content tabs

When the 'GENERATE_ECLIPSE_HELP' and 'GENERATE_TREEVIEW' options is set to 'YES", Doxygen produces badly formatted content. See attached screenshot for example. 
This is due to wrongly computed value in 'top' propert. It is computed in resize.js file, 'resizeHeight' method, last line. I can reproduce the issue with Firefox 24.2.0 and Chrome 45.0.2454.93 (latest).
Also, we found that the issue can be fixed by *NOT* recomputing the 'top' value on every screen resize - by simply remove the 'top: headerHeight+"px"' part of the Javascript clause and let browser to compute screen position itself.
The fix is tested on aforementioned browser versions.
Proposed fix is also attached to this bug

Comment 1 Slava Risenberg 2015-09-20 07:04:24 UTC

Created attachment 311691 [details] [review]
Proposed fix

Comment 2 Slava Risenberg 2015-09-20 07:09:01 UTC

I can reproduce the bug on 1.8.10 as well...

Comment 3 Dimitri van Heesch 2015-09-20 13:54:06 UTC

Thanks, I'll include the patch in the next GIT update.

Comment 4 Dimitri van Heesch 2015-12-30 10:19:36 UTC

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.11. 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).