GNOME Bugzilla – Bug 767585
Middle-clicking the title bar doesn't send Epiphany to the background
Last modified: 2016-06-16 14:24:33 UTC
Steps to reproduce 1. Middle-click the titlebar of an Epiphany window Expected behaviour: - Epiphany window is sent to the background Actual behaviour: - Nothing happens.
I'm confused, why would you expect this behavior? I tested several apps and middle clicking the title bar doesn't do anything for any of them. What desktop environment are you using -- does your window manager implement this behavior? What happens if you middle click the title bar in another app that uses GtkHeaderBar (e.g. nautilus)?
I'm using GNOME 3.20 (with gnome-shell). The action of middle-clicking can be customized with GNOME Tweak Tool, which changes the org.gnome.desktop.wm.preferences action-middle-click-titlebar setting. dconf-editor tells me "lower" is the default value for this setting! Nautilus and gnome-terminal both lower the window when I middle-click their headerbars. AFAIU this is implemented in the standard GtkHeaderBar widget. Experimenting a little bit more I see that if I click near the edges of Epiphany's headerbar, I get the expected lowering action, but if I click on the text in the middle, or in the margins around it (which are part of the EphyTitleBox, according to GTK Inspector), then nothing happens.
OK, I wonder if I broke it in bug #744307. If you happen to be a developer, you could check by reverting that patch. Otherwise... we want to remove that title box anyway, so this will get fixed when that happens.
Yes, reverting commit 25df8678f43c26f990b07a758516585a91811df6 makes this bug go away.
Well since it didn't fix anything, let's do that.
The following fix has been pushed: e94904e Revert "title-box: Do not propagate button press events in title mode"
Created attachment 329801 [details] [review] Revert "title-box: Do not propagate button press events in title mode" This reverts commit 25df8678f43c26f990b07a758516585a91811df6.
Fix will be in next week's 3.20.3 release. Thanks for reporting.
*** Bug 767728 has been marked as a duplicate of this bug. ***