Re: is metacity _really_ ICCCM-compliant ?
- From: Rob Adams <readams readams net>
- To: wm-spec-list gnome org
- Subject: Re: is metacity _really_ ICCCM-compliant ?
- Date: Tue, 07 Sep 2004 09:03:57 -0700
Metacity doesn't set the window type for menus; that's the
responsibility of the owning application. Most popup menus though are
override redirect, which means that the window type and transient hint
is totally irrelevant; these would only matter for a managed window.
So this is certainly not a metacity bug, though it may arguably be a
very minor cosmetic gtk bug. But as for bugs on specific
implementations, you should report bugs directly to the relevant bug
tracking system; for gnome:
http://bugzilla.gnome.org
-Rob
On Tue, 2004-09-07 at 09:53 +0200, Michael Boccara wrote:
> When querying properties of metacity's windows, I noticed they are not
> really compliant with the specs described in
> http://freedesktop.org/Standards/wm-spec/1.3
>
> For example, when querying the _NET_WM_WINDOW_TYPE of a popup menu, I should
> get _NET_WM_WINDOW_TYPE_MENU and have the WM_TRANSIENT_FOR atom set to my
> application window.
> Instead, the type is _NET_WM_WINDOW_TYPE_NORMAL, and WM_F|TRANSIENT_FOR is
> not set.
>
> I am using
> Red Hat Advanced Server 3.0
>
> Is the lack of ICCCM-compliancy a known issue for metacity ?
> Because the following page
> http://cvs.gnome.org/viewcvs/metacity/COMPLIANCE?view=markup
> pretends that metacity is compliant, at least concerning the
> _NET_WM_WINDOW_TYPE property
>
> Thanks,
>
> Michael
>
> _______________________________________________
> wm-spec-list mailing list
> wm-spec-list gnome org
> http://mail.gnome.org/mailman/listinfo/wm-spec-list
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]