Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

workspace switcher: keyboard trap when moving on it with the keyboard #952

Closed
alexarnaud opened this issue Apr 9, 2019 · 13 comments · Fixed by #958
Closed

workspace switcher: keyboard trap when moving on it with the keyboard #952

alexarnaud opened this issue Apr 9, 2019 · 13 comments · Fixed by #958

Comments

@alexarnaud
Copy link
Member

alexarnaud commented Apr 9, 2019

Expected behaviour

Same behavior as in earlier releases (< 1.22): only the context menu key opens the context menu.

Actual behaviour

The workspace switcher handles all keys and open the context menu so it's not possible to leave it without a mouse. In short term, a blind user or keyboard-only user is blocked on the workspace switcher.

Steps to reproduce the behaviour

  1. Enable the default Mate layout to ensure a easier reproduction
  2. Press control + alt + tab to move to the bottom panel (or control + alt + espace on Ubuntu)
  3. Move on the workspace switcher if you're not on it already
  4. Press tab or try to leave the panel with control + alt + tab

MATE general version

1.22.0

Linux Distribution

Both Fedora 30 and Arch Linux

Link to downstream report of your Distribution

Pointed to me by a blind user on the orca list: https://mail.gnome.org/archives/orca-list/2019-April/msg00019.html

@alexarnaud alexarnaud changed the title worksapce switcher: keyboard trap when moving on it with the keyboard workspace switcher: keyboard trap when moving on it with the keyboard Apr 9, 2019
@vkareh
Copy link
Member

vkareh commented Apr 9, 2019

It happens also with the window-list and with the clock applets. Once focused, pressing any key will trigger the context menu, so a keyboard-only user will be stuck.

@alexarnaud
Copy link
Member Author

alexarnaud commented Apr 10, 2019 via email

@alexarnaud
Copy link
Member Author

@raveit65 @lukefromdc @vkareh This is a regression, could you help us to figure out this one ?

This issue makes Mate Panel 1.22 really difficult to use for a keyboard-only user like a blind person.

Best regards,
Alex.

@lukefromdc
Copy link
Member

lukefromdc commented May 3, 2019 via email

@raveit65
Copy link
Member

raveit65 commented May 3, 2019

I hope that is a regression caused by MATE and not by gtk+, because I noticed other issues with menus in f30.
But maybe that is another fallout out by fixing deprecated gtk_menu_popup.

@lukefromdc
Copy link
Member

it in indeed from fixing deprecated gtk_menu_popup and affects other applets using mate-panel-applet.c as well.
dacbd08
" mate-panel-applet.c: replace deprecated gtk_menu_popup"
is the offending commit-and I noticed that prior to it, neither the panel tasklist, nor other wncklet apps could be interacted with by the keyboard at all (at least with what I was doing) other than to tab past them and keep going. Now the window list, show-desktop, plus the clock, trash etc all open their menus when tab is pressed again once they are focussed.

@lukefromdc
Copy link
Member

I just found that gnome-panel also has this keyboard trap

@lukefromdc
Copy link
Member

So how to we get the tab to continue through, but return to pop up the menu?

@lukefromdc
Copy link
Member

#958 fixes the keyboard trap, sets the context menus to open only on the menu key. Can't use return for this as it is needed for things like opening the calendar. Some applets (notably the new volume control panel applet) will need further work to traps properly use the "return" keypress as some others (e.g. the clock/calendar) already do or partially do with this.

Also: note that ESC will exit the menus with current master and get out of the keyboard trap, and also escape menus opened in the PR version of mate-panel with the menu key

@alexarnaud
Copy link
Member Author

alexarnaud commented May 7, 2019 via email

@alexarnaud
Copy link
Member Author

Does this fix has been backported to 1.22 branch ?

Mate 1.22 lands into Debian unstable and a blind colleague told me that the bug occurs on Debian too.

The Debian issue is: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933714

Best regards,
Alex.

@raveit65
Copy link
Member

raveit65 commented Aug 2, 2019

@alexarnaud
Copy link
Member Author

@raveit65 Thanks so it has been backported but no released has been published since that.

We'll wait the next release point.

Best regards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants