Fix tap regression

By removing tap, we caused a regression in the uicatalog/clear-specs tests. The problem with the "tap" strategy isn't that it's not reliable, it's that there are an infinite number of ways to close the keyboard.  It's ultimately up to the developer, so all we can do in hideKeyboard is provide a few of the most common strategies. Tapping on the background is a common strategy, so it should remain in the code.
are you sure this is an upward swipe? I thought it was down.