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 698841 - regression: gedit window resizes when opening/closing a document
regression: gedit window resizes when opening/closing a document
Status: RESOLVED DUPLICATE of bug 696882
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-04-25 14:09 UTC by Adam Dingle
Modified: 2013-04-25 14:58 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Adam Dingle 2013-04-25 14:09:29 UTC 
With GTK built from git master:

1. Start gedit.  You'll have a single tab showing an Unsaved Document.
2. Resize the window to be smaller or larger.
3. Close the tab.  The window snaps back to its previous size.
4. Resize the window to be smaller or larger.
5. Open a document in gedit.  The window snaps back to its previous size.

The window size should not change when documents are opened or closed.

I'm filing this as a GTK bug since it happens with newer versions of GTK, independently of the gedit version.  This did not occur with GTK 3.8.0.
Comment 1 Adam Dingle 2013-04-25 14:58:33 UTC 
I bisected, and found this broke here:

commit 21f11eb0e6bcdeb39cf9de184387008d7d9e8286
Author: Benjamin Otte <otte@redhat.com>
Date:   Mon Apr 8 16:25:29 2013 +0200

    window: restore size after hide/show properly
    
    Old code assumed the size was stored in widget.allocation. This is no
    longer true as the allocation is cleared upon hide. However, we store
    the last configure request, and that one tracks the last size, so we can
    just use that number.
    
    Sometimes things are so easy - once you figure them out...
    
    https://bugzilla.gnome.org/show_bug.cgi?id=696882

So this is evidently another symptom of the open problem described in bug 696882.  Marking as a duplicate.
Comment 2 Adam Dingle 2013-04-25 14:58:47 UTC 

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