Frame shadow of gtk3 application is not transparent for mouse clicks

Bug #1521586 reported by b3nmore on 2015-12-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gtk+3.0 (Ubuntu)

Bug Description

The shadow region of Gtk3 apps drawing their own frame shadow (CSD) is not transparent for mouse events. E.g. when such an app is in front of a browser window, a link in the browser can only be clicked/hovered at distance from the window border, which is larger than the shadow thickness.

This may be related to #1518661.

b3nmore (b3nmore) wrote :

This affects gtk3 indicator in Xubuntu (xfwm or mutter as wm). Usually the black borders in the attached screenshot are transparent shadows, but it represents exactly the area which is sometimes not clickable.

To reproduce:
* click a gtk3 indicator
* hover over the expanded indicator menu
* try to click the indicator or any neighbors
=> only clicks in the upper ~1/3 of the button show a reaction, the lower 2/3 do nothing.

The same thing happens with some gtk3 window shadows, e.g. the gnome calculator: Underlying windows cannot be brought into focus near the window border in the shadow area.

Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu Package testing tracker.

A list of all reports related to this bug can be found here:

tags: added: package-qa-testing
b3nmore (b3nmore) wrote :

So, its not the shadow actually, which would have been weird in the first place. But some apps (I would say gtk3, csd; eg. gnome-calculator, gnome-software) show a different behavior concerning window border grabbing (for resizing). Windows, which can be resized, change the cursor the discussed area next to the window border and can be resized. This behavior is probably also applied to windows, which can not be resized, like gnome-calculator or the indicator menus. Thus leading to the several pixel wide region near window borders, where mouse clicks are not interpreted as, well, clicks.

If the border grabbing margin is intentional (although it leads to an inconsistent behavior between different apps), then it should be disabled for windows, which are not resizeable.

b3nmore (b3nmore) wrote :

I should mention, that I get this issue only with enabled compositing in the wm. In my case with xfwm or mutter (cf. attached screenshot).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers