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

Accessiblity: Brisk vs onBoard #15

Open
gripfastistech opened this issue Aug 19, 2019 · 1 comment
Open

Accessiblity: Brisk vs onBoard #15

gripfastistech opened this issue Aug 19, 2019 · 1 comment

Comments

@gripfastistech
Copy link

Accessbility: Brisk vs Onboard

When using a device without a keyboard such as a tablet on direct touchscreen, the Brisk Menu along with its top search field assumes/overrides the top most input layer position making it impossible to use the Accessiblity virtual keyboard Onboard to search for specific apps and programs.

This was originally opened under Ubuntu MATE then moved to Ubuntu proper. Any thoughts?

Basically this is killing Brisk use on a tablet without a keyboard.

@trappedinspacetime
Copy link

I have the same issue. Due to my disease I need to use only onboard for the input. Brisk search box immediately loses focus when I try to type. So, searching with virtual keyboard is not possible in Brisk Menu's search box.

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

No branches or pull requests

2 participants