Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

updating readme

  • Loading branch information...
commit 8f715de26531fcb5e48540130668a81f7bd6916e 1 parent 3de62a3
@davidcalhoun authored
Showing with 13 additions and 3 deletions.
  1. +13 −3 README
View
16 README
@@ -1,5 +1,15 @@
-Why use energize? Because touch devices sometimes add an artificial delay to click events, just to make sure the user isn't double-tapping to zoom.
+------------
+Why use energize?
-Why not just bind to ontouchend? Because the user might touch an element to scroll. Do you want a click event to fire when the user was intending to scroll?
+Touch devices sometimes add an artificial delay to click events, just to make sure the user isn't double-tapping to zoom.
-Why fire simulated touch events? Why not just use something like Fast Button (http://code.google.com/mobile/articles/fast_buttons.html)? Because you have to add click events to EVERYTHING you want to speed up. Also, interaction with native form elements such as buttons aren't sped up unless you manually add events to them. Energize listens for clicks bubbling up to the top and handles them appropriately so you don't have to worry about them.
+Why not just bind to ontouchend?
+-------------
+
+Because the user might touch an element to scroll. Do you want a click event to fire when the user was intending to scroll?
+
+
+Why fire simulated touch events? Why not just use something like <a href="http://code.google.com/mobile/articles/fast_buttons.html">Fast Button</a>?
+-------------
+
+Because you have to add click events to EVERYTHING you want to speed up. Also, interaction with native form elements such as buttons aren't sped up unless you manually add events to them. Energize listens for clicks bubbling up to the top and handles them appropriately so you don't have to worry about them.
Please sign in to comment.
Something went wrong with that request. Please try again.