8 Commits

Author	SHA1	Message	Date
Adam Bradley	79f6b251c3	test(tap): Tests for ignoreTapInspect, recordCoordinates, isRecentTap	2014-04-07 11:07:31 -05:00
Adam Bradley	9d83b05580	test(tap): split apart ignoreSimulateClick tests	2014-04-07 10:01:53 -05:00
Adam Bradley	a977332f2b	fix(tap): Do not preventDefault after input focus, #1068	2014-04-07 09:43:41 -05:00
Adam Bradley	e3c59e96a9	test(tap): add some more tests for taps	2014-04-07 00:44:29 -05:00
Adam Bradley	cf686548da	fix(tap): Remove 300ms delay when tapping select elements	2014-04-05 23:43:12 -05:00
Adam Bradley	cb602b587b	fix(tap): Prevent clicks from firing after scrolling, #579	2014-04-04 12:28:42 -05:00
Adam Bradley	3ee5ea77a6	fix(tap): Deactivate elements during scroll at the same time click is ignored, #997 ... Previously I disabled the activation class immediately on a touchmove, where as the click will still work if you touchstart and touchend within a few pixels of each other. So visually it may have looked like the click shouldn't have worked. I just updated it so the use the same numbers. For example, if you hold down an item and move just 5 pixels, the item will stay active (before it wouldn't have), and the click will fire. But at the same time, if you hold down an item, and move a larger distance, once it realizes that it went farther than 6 pixels it'll not allow a click to happen, AND it'll not show the item as being active.	2014-04-03 23:24:31 -05:00
Adam Bradley	0c1362861d	refactor ionic.tap and start writing tests	2014-04-03 13:52:48 -05:00