Sometimes the first click (press-and-releasse) on the places plugin in my panel does nothing. A second click is needed to actually open it. Unfortunately I cannot reproduce this yet, it appears to be happening somewhat randomly.
It seems that when this happens, the first click sometimes briefly opens the menu. As if the user had long-clicked, except the timeout was way too short.
My panel size is 28 pixels and it's near a screen edge. the places plugin is set to icon only. When I move the cursor onto the plugin right at the edge of the screen, there seems to be a chance for the places plugin to not get mouse focus.
Move the mouse onto the places plugin while hugging the screen edge. The plugin will sometimes react to clicks, and sometimes not. It will sometimes highlight, and sometimes not. Even if the icon is highlighted, this doesn't mean it will react to clicks properly.
If this bug doesn't trigger for you, try moving the cursor a little, or move it off the plugin and on again (but always stay at the screen edge)
Thanks for your help, I appreciate 👍
I'm able to reproduce it, even with my own size of panel (36 pixels) and with others plugins (powermanager, weather).
It seems to me that it occurs only when I continue to push my mouse up (my panel is on the upper side of the screen) and simultaneously I click on the plugin.
I noticed that it doesn't affect all components. @Tamaranch this bug is not only a places-plugin bug, but not sure it'a a panel bug or a "plugin" bug because of the way some of them use the panel or react.
Can you reproduce it too?
Yes it is reproducible with any external plugin I think. I can only reproduce it with the panel on the left or top of the screen (by pushing the pointer off screen so the plugin loses/gains focus).
Strangely enough, it doesn't seem to be reproducible when there are only external plugins (e.g. running the panel with the hidden force-all-external option set to true). So a mix of internal and external plugins would be needed.
Also it's only reproducible on X11, so it could be related to something internal to GtkSocket/GtkPlug.
Moving this to the panel anyway, but don't expect to see it fixed right away, if ever.