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 98233 - Layers in mozilla does not seem to receive all mouse events.
Layers in mozilla does not seem to receive all mouse events.
Status: RESOLVED DUPLICATE of bug 102209
Product: metacity
Classification: Other
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2002-11-11 18:09 UTC by Johan (not receiving bugmail) Dahlin
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0

Attachments
Test case (1.00 KB, text/html)
2002-11-11 18:10 UTC, Johan (not receiving bugmail) Dahlin 		Details

Description Johan (not receiving bugmail) Dahlin 2002-11-11 18:09:34 UTC 






Comment 1


Johan (not receiving bugmail) Dahlin





          2002-11-11 18:10:14 UTC
        



Created attachment 12228 [details]
Test case






Comment 2


Havoc Pennington





          2002-11-12 00:02:44 UTC
        



I can reproduce, but I don't think the layer is a separate toplevel
GdkWindow (doesn't seem to be in metacity logs), so I don't understand
how metacity could have anything to do with it.







Comment 3


Heath Harrelson





          2002-11-18 18:42:45 UTC
        



Is this NOTGNOME or NOTABUG?  Is it left open for some reason?






Comment 4


Christopher Blizzard





          2002-12-02 18:14:52 UTC
        



Havoc, we talked about this at length.  Any ideas what we can do?






Comment 5


Havoc Pennington





          2003-02-25 21:21:03 UTC
        



I believe the plan is to drop button grabs on the focused window
or something. (Seems awfully racey, but probably a good idea.)






Comment 6


Havoc Pennington





          2003-02-25 21:38:46 UTC
        




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