GNOME Bugzilla – Bug 325673
Workspace switcher is not clickable on the far edge if panel background is changed to Solid color
Last modified: 2015-03-24 13:00:56 UTC
Please describe the problem: The workspace switcher can be placed in a corner to allow easy access using "Fitt's law" by placing the cursor in the corner and click. However, if the panel's background is changed from "None (use system theme)" to "Solid color", the workspace switcher somehow gets a border, making it impossible to switch workspace by clicking in the corner. Steps to reproduce: 1. Place a workspace switcher in the corner of an expanded panel. Test Fitt's law by clicking on the edge of the panel and verify that the workspace is switched. 2. Change the panel background to "Solid color" 3. Try clicking on the edge of the panel again. Actual results: The workspace isn't switched. You need to aim the mouse pointer inside the workspace switcher to actually switch. Expected results: It should have worked the same way regardless of panel background. Does this happen every time? Yes. Other information: Tested in Clearlooks. I doubt it's a theme issue though.
The issue here is that the workspace switcher is not in the corner of the panel any more. I guess you're using a right or bottom corner? If you move the applet after changing the background, does it work? If so, then I think there's already a bug about the fact that we should use relative coordinates. Need to find it, though.
No, even if I move it after changing the background, it's still not clickable on the edges. It's not just the corner-pixel that is affected, but both sides facing the corner. It's not possible to move the applet more to the corner, and it always fills the entire height of the panel anyway.
Reopening. Setting target to 2.14 so I'll look at it when I'll have time.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. Many thanks for the solid color hint, although it was suggested I didn't check for it. *** This bug has been marked as a duplicate of 304248 ***