Mir

Input events on non-input clients pass straight through to the surface below

Bug #1321557 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Unassigned

Bug Description

Input events on non-input clients pass straight through to the surface below (if any). This is particularly confusing when the non-input app on top is opaque and you can't see that you're interacting with the surface below it.

Test case:
  1. Start mir_demo_server_shell
  2. Start mir_demo_client_fingerpaint
  3. Start mir_demo_client_egltriangle or any other non-input client, on top of fingerpaint
  4. Click and drag in the egltriangle window. Nothing happens (correctly).
  5. Alt-Tab to see fingerpaint that was below.
Expected: Fingerpaint shows nothing.
Observed: Fingerpaint shows markings from clicking and dragging on the egltriangle window.

Obviously we're passing input events down to the first surface that consumes them. However for simple opaque non-input surfaces, this is very confusing and misleading. We need to ensure touch/mouse events don't get sent to obscured client surfaces below.

Tags: input
Revision history for this message
Alan Griffiths (alan-griffiths) wrote :

Sometime in the past three years this got fixed.

Changed in mir:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.