Mir

Clients don't receive motion events originated inside their own rectangle if they have been moved/resized

Bug #1261647 reported by Daniel van Vugt
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mir
Fix Released
High
Robert Carr
mir (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Clients don't receive motion events inside their own rectangle if they have been moved/resized.

On startup, everything seems fine. Clients get touch events for any gesture which began inside the client surface rectangle.

But if you move/resize the surface (mir_demo_server_shell), then you will find the client only gets motion events if the gesture is initiated inside the surface's original creation rectangle. It doesn't pay any attention to the surface's new position/size.

To see events in the server:
   bin/mir_demo_server_shell --input-report=log
And then look for the same events reaching the client:
   env MIR_CLIENT_INPUT_RECEIVER_REPORT=log bin/mir_demo_client_egltriangle

If you move the client to a new location (Alt+drag), then the client report shows input events only when the mouse is over the original creation area, not the client's actual area.

See also (related but different) bug 1268819.

Tags: input

Related branches

description: updated
summary: - Clients don't receive touch events inside their own rectangle if they
+ Clients don't receive motion events inside their own rectangle if they
have been moved/resized
description: updated
Changed in mir:
milestone: 0.1.3 → 0.1.4
Changed in mir:
milestone: 0.1.4 → 0.1.5
summary: - Clients don't receive motion events inside their own rectangle if they
- have been moved/resized
+ Clients don't receive motion events originated inside their own
+ rectangle if they have been moved/resized
description: updated
Changed in mir:
milestone: 0.1.5 → none
Revision history for this message
kevin gunn (kgunn72) wrote :
Changed in mir:
status: Triaged → New
status: New → Triaged
Changed in mir:
assignee: nobody → Andreas Pokorny (andreas-pokorny)
Changed in mir:
status: Triaged → In Progress
Changed in mir:
milestone: none → 0.1.7
Changed in mir:
status: In Progress → Triaged
description: updated
Changed in mir:
status: Triaged → In Progress
Changed in mir:
milestone: 0.1.7 → 0.1.8
Changed in mir:
milestone: 0.1.8 → 0.1.9
kevin gunn (kgunn72)
Changed in mir:
milestone: 0.1.9 → 0.1.10
Changed in mir:
assignee: Andreas Pokorny (andreas-pokorny) → Robert Carr (robertcarr)
Changed in mir:
milestone: 0.2.0 → 0.3.0
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir/devel at revision None, scheduled for release in mir, milestone Unknown

Changed in mir:
status: In Progress → Fix Committed
Changed in mir:
status: Fix Committed → Fix Released
Changed in mir (Ubuntu):
status: New → Fix Released
importance: Undecided → High
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.