title: Is disabling all click events at first touchstart event a good idea?
body: <p>Making a nice quick-responding website is relatively difficult because of the conflicts between touchstart, tap and the 300ms delayed click.</p>
  
  <p>Ofcourse <code>vclick</code> should fix these issues, but also they seem to have problems fixing it completely. From the documentation:</p>
  
  <blockquote>
    <p><strong>Warning: Use vclick with caution</strong></p>
    
    <p>Use vclick with caution on touch devices. Webkit based browsers
    synthesize mousedown, mouseup, and click events roughly 300ms after
    the touchend event is dispatched. The target of the synthesized mouse
    events are calculated at the time they are dispatched and are based on
    the location of the touch events and, in some cases, the
    implementation specific heuristics which leads to different target
    calculations on different devices and even different OS versions for
    the same device. This means the target element within the original
    touch events could be different from the target element within the
    synthesized mouse events.</p>
    
    <p>We recommend using click instead of vclick anytime the action being
    triggered has the possibility of changing the content underneath the
    point that was touched on screen. This includes page transitions and
    other behaviors such as collapse/expand that could result in the
    screen shifting or content being completely replaced.</p>
  </blockquote>
  
  <p>Now I'm thinking about doing something simpler. Whenever a touchstart event is being triggered I know this is a touch device for sure. I just disable all click events, and start listening to touchstart (or tap) events <em>only</em>. Ignoring the 300ms delayed click events.</p>
  
  <p>Of course there are devices with a mouse <em>and</em> touch, but people using these at the same time seem like a minority to me.</p>
  
  <p>Is this a good idea, or am I missing something in my thinking?</p>