Carlos Garnacho bbfa616f27 grabHelper: consume the press/motion/release sequence if a press dismisses the grab ... The grab would previously just consume the button release, while propagating motion events, possibly down to clients in wayland. This would produce inconsistent streams there. On pointer events, the inconsistency would just be having clients receiving events with the button 1 set in the mask, with no implicit grab. When touch events are handled, this would be more hindering as the client would receive touch_motion events with no prior touch_down nor later touch_up, something never supposed to happen. https://bugzilla.gnome.org/show_bug.cgi?id=733633		2014-07-31 10:55:11 +02:00
..
extensionPrefs	extensionPrefs: Respect 'disable-extension-version-validation' setting	2014-07-18 10:47:02 +02:00
gdm	loginDialog: Push a modal for LOCK_SCREEN	2014-07-27 08:18:51 -04:00
misc	util: Don't pass too many arguments to child_watch_add	2014-04-28 10:22:51 -04:00
perf	hwtest: Handle rename of gedit desktop file	2014-07-25 10:40:45 +02:00
portalHelper	portalHelper: fix typo	2014-06-26 20:10:18 +02:00
ui	grabHelper: consume the press/motion/release sequence if a press dismisses the grab	2014-07-31 10:55:11 +02:00
js-resources.gresource.xml	Add a new hwtest script	2014-07-16 10:37:48 -04:00
Makefile.am	js/Makefile.am: Fix dependency generation with srcdir != builddir	2014-06-29 18:27:53 -04:00