Missing client API to indicate some windows should never receive keyboard focus
Bug #1671771 reported by
Daniel van Vugt
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
New
|
High
|
Unassigned | ||
| mir (Ubuntu) |
New
|
High
|
Unassigned | ||
Bug Description
Missing client API to indicate some windows should never receive keyboard focus.
According to the Unity8 design:
<mpt> duflu, yes, the “gloss” and “tip” types are unfocusable, and an app/toolkit should be able to specify whether a particular “freestyle” window is unfocusable. <https:/
But Xmir has broader requirements that menus and utility windows should have the option of being unfocusable. This is required to fix bug 1625846 and bug 1671744. Maybe also bug 1662733.
| description: | updated |
| Changed in mir: | |
| milestone: | 0.27.0 → 0.28.0 |
Revision history for this message
| Michał Sawicz (saviq) wrote | #1 |
| Changed in mir (Ubuntu): | |
| importance: | Undecided → High |
To post a comment you must log in.
Syncing task from Mir.