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 345406 - GtkNotebook occasionally cuts off tabs when it should scroll
GtkNotebook occasionally cuts off tabs when it should scroll
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: GtkNotebook
2.8.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 345537 345912 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-06-20 10:30 UTC by Chris Lord
Modified: 2006-07-18 01:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
Screenshot of bug (16.74 KB, image/png)
2006-06-20 10:31 UTC, Chris Lord 		Details

Description Chris Lord 2006-06-20 10:30:53 UTC 
Please describe the problem:
It seems if the notebook is almost full and a new tab is created that should cause it to scroll and immediately switched to, the scroll arrows don't appear. This bug is apparent in gedit when creating a new document with the notebook almost full. The arrows reappear as soon as another tab is activated.

Steps to reproduce:
1. Open gedit
2. Create new windows until the notebook scroll arrows should appear
3. Note that they don't


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Chris Lord 2006-06-20 10:31:33 UTC 
Created attachment 67693 [details]
Screenshot of bug
Comment 2 Matthias Clasen 2006-06-21 14:33:57 UTC 
What version is this with, exactly ?  

There is a patch to fix this in the tip of the gtk-2-8 branch.
It would be great if you could test that it fixes the issue.

I'll do a 2.8.x release with the fix soon.
Comment 3 Chris Lord 2006-06-21 14:36:00 UTC 
This is with 2.8.18, latest from Ubuntu dapper.
Comment 4 Matthias Clasen 2006-06-21 15:08:02 UTC 
*** Bug 345537 has been marked as a duplicate of this bug. ***
Comment 5 Reinout van Schouwen 2006-07-17 21:48:31 UTC 
*** Bug 345912 has been marked as a duplicate of this bug. ***
Comment 6 Matthias Clasen 2006-07-18 01:41:54 UTC 
Should  be fixed in 2.8.20