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 675874 - Race between maximise and resizable
Race between maximise and resizable
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: Other
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-05-11 13:35 UTC by Bastien Nocera
Modified: 2018-02-10 03:44 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
test case (1.10 KB, text/plain)
2012-05-11 13:35 UTC, Bastien Nocera 		Details

Description Bastien Nocera 2012-05-11 13:35:51 UTC 
Created attachment 213868 [details]
test case

Probably a bug in GTK+' interaction with the window managers.

Doing:
gtk_window_set_resizable (GTK_WINDOW (self->priv->window), TRUE);
gtk_window_maximize (GTK_WINDOW (self->priv->window));
Fails.

Doing:
gtk_window_set_resizable (GTK_WINDOW (self->priv->window), TRUE);
[wait a bit]
gtk_window_maximize (GTK_WINDOW (self->priv->window));
Works.

Tested with GTK+ from master.

See also https://bugzilla.gnome.org/show_bug.cgi?id=673869#c47 for reproducer in gnome-control-center.
Comment 1 Bastien Nocera 2012-05-21 17:05:21 UTC 
There's a similar problem with:
gtk_window_set_resizable (GTK_WINDOW (self->priv->window), TRUE);
gtk_scrolled_window_set_min_content_height (GTK_SCROLLED_WINDOW (self->priv->scrolled_window), SMALL_SCREEN_FIXED_HEIGHT);

Where the window would only change size again when window focus changes.

Do we need an async gtk_window_set_resizable()? Should GTK+ buffer those changes to be done after we know the window manager has processed resizable having changed?
Comment 2 Matthias Clasen 2018-02-10 03:44:55 UTC 
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.