Mir emits a mir_motion_action_hover_exit event before of a mir_motion_action_pointer_down
Bug #1419048 reported by
Marco Trevisan (Treviño)
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Robert Carr | ||
mir (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
This breaks toolkits such as gtk and clutter as this causes the input widget to be reset and thus not to get the pointer-down event.
Related branches
lp:~mir-team/mir/new-input-dispatcher
- PS Jenkins bot (community): Approve (continuous-integration)
- Alexandros Frantzis (community): Approve
- Andreas Pokorny (community): Approve
- Chris Halse Rogers: Approve
- Alberto Aguirre: Pending requested
-
Diff: 2383 lines (+1729/-73)35 files modifiedinclude/client/mir/events/event_builders.h (+4/-0)
include/server/mir/input/input_dispatcher.h (+2/-1)
include/server/mir/time/alarm.h (+0/-1)
src/client/events/event_builders.cpp (+13/-0)
src/include/platform/mir/options/configuration.h (+3/-0)
src/include/server/mir/default_server_configuration.h (+6/-2)
src/platform/options/default_configuration.cpp (+4/-1)
src/platform/symbols.map (+1/-0)
src/server/input/CMakeLists.txt (+3/-0)
src/server/input/android/android_input_dispatcher.cpp (+2/-1)
src/server/input/android/android_input_dispatcher.h (+1/-1)
src/server/input/android/default_dispatcher_policy.cpp (+3/-3)
src/server/input/android/default_dispatcher_policy.h (+1/-3)
src/server/input/default_configuration.cpp (+26/-27)
src/server/input/event_filter_chain_dispatcher.cpp (+4/-3)
src/server/input/event_filter_chain_dispatcher.h (+1/-1)
src/server/input/key_repeat_dispatcher.cpp (+138/-0)
src/server/input/key_repeat_dispatcher.h (+71/-0)
src/server/input/null_input_dispatcher.cpp (+2/-2)
src/server/input/null_input_dispatcher.h (+2/-1)
src/server/input/surface_input_dispatcher.cpp (+474/-0)
src/server/input/surface_input_dispatcher.h (+114/-0)
src/server/symbols.map (+3/-1)
tests/acceptance-tests/test_client_input.cpp (+40/-2)
tests/acceptance-tests/test_custom_input_dispatcher.cpp (+2/-2)
tests/include/mir_test/event_matchers.h (+29/-4)
tests/include/mir_test_doubles/mock_input_dispatcher.h (+1/-1)
tests/include/mir_test_doubles/mock_surface.h (+6/-0)
tests/integration-tests/input/test_cursor_listener.cpp (+1/-4)
tests/mir_test_framework/headless_test.cpp (+1/-0)
tests/unit-tests/input/CMakeLists.txt (+2/-0)
tests/unit-tests/input/android/test_android_input_targeter.cpp (+2/-1)
tests/unit-tests/input/test_key_repeat_dispatcher.cpp (+121/-0)
tests/unit-tests/input/test_surface_input_dispatcher.cpp (+646/-0)
tests/unit-tests/scene/test_surface_impl.cpp (+0/-11)
Changed in mir: | |
milestone: | 0.11.0 → 0.12.0 |
Changed in mir: | |
status: | Triaged → In Progress |
Changed in mir: | |
milestone: | 0.12.0 → 0.13.0 |
Changed in mir (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in mir: | |
milestone: | 0.13.0 → 0.14.0 |
Changed in mir: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Really in progress? Fixed somewhere already?