Bug 172204 - Statusbar and scrollbar are transparent in tab mode
Summary: Statusbar and scrollbar are transparent in tab mode
Status: RESOLVED DUPLICATE of bug 171508
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-05 14:32 UTC by Anne-Marie Mahfouf
Modified: 2009-01-16 22:52 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
konq statusbar and scrollbar is showing other tab content (156.35 KB, image/png)
2008-10-05 14:34 UTC, Anne-Marie Mahfouf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anne-Marie Mahfouf 2008-10-05 14:32:56 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

No desktop effects, it happens when starting Konqueror in tab mode, not sure since when.
See attached screenshot
Comment 1 Anne-Marie Mahfouf 2008-10-05 14:34:37 UTC
Created attachment 27700 [details]
konq statusbar and scrollbar is showing other tab content
Comment 2 Sune Vuorela 2008-10-05 14:36:32 UTC
I also see it quite often, especially when letting the crash recovery thingie recover.
Comment 3 Juan Carlos Torres 2008-10-05 15:12:15 UTC
I've also had this happen, usually when I load a view profile which has multiple tabs saved. I open a clean Konqueror instance, nothing wrong with statusbar, then Load View Profile, and then it becomes like that. opening or closing tabs doesn't consistently make it go away.
Comment 4 Jonathan Thomas 2008-11-16 15:44:17 UTC
I believe the problem is that the KHTML part renders before the statusbar and scrollbar appear. This makes the KTHML part think that it can draw over a larger area than it really can.
Comment 5 George Kiagiadakis 2009-01-16 22:52:50 UTC
There is a testcase for that in bug 171508 if you are interested... :)

*** This bug has been marked as a duplicate of bug 171508 ***