[Bug 129916] Changed - breaks xemacs maximisation

[bugzilla-daemon@widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=129916

Changed by readams@hmc.edu.

--- shadow/129916	Tue Dec 23 15:48:20 2003
+++ shadow/129916.tmp.19667	Tue Dec 23 16:48:19 2003
@@ -21,6 +21,24 @@
 
 "Hello. Latest metacity upgrade breaks xemacs-mule: after launching xemacs,
 if maximising completely (not just horizontal or vertical) causes xemacs to
 enter some kind of loop with the display flickering.
 
 Other programs seem not affected."
+
+------- Additional Comments From readams@hmc.edu  2003-12-23 16:48 -------
+this has got to be a bug in xemacs.  When metacity maximizes a window,
+it does two things: first, it does the move/resize, which results in a
+ConfigureNotify being sent to the window, either by metacity or by the
+X  server.  Second, it update the _NET_WM_STATE window property to
+include the _NET_WM_STATE_MAXIMIZED_VERT and
+_NET_WM_STATE_MAXIMIZED_HORZ.  This will result in a PropertyNotify
+event being sent to the client if it's watching for such events.
+
+If xemacs is getting into a loop, it must be responding to the
+ConfigureNotify or the PropertyNotify in some incorrect manner.  Not
+really sure what was changed in metacity 2.6.2 to bring out this
+behavior in xemacs, but if it's not metacity that's looping, I'd be
+surprised if this is a bug in metacity.
+
+I'll go ahead and test out this on xemacs to try to see what's going
+on before I mark NOTGNOME though.