<h3 dir="auto">Problem description</h3>
<p dir="auto">After <code class="notranslate">onTouchTap</code> was handled, button doesn't leave hover state, until you hove it once again.</p>
<h3 dir="auto">Steps to reproduce</h3>
<ul dir="auto">
<li>go over button, hover style takes place</li>
<li>click button, new tab is opened</li>
<li>go back to old tab</li>
<li>expected: button is in normal state</li>
<li>actual: button is in hover satte</li>
</ul>
<h3 dir="auto">Versions</h3>
<ul dir="auto">
<li>Material-UI: 15.0 (commit: <a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/mui/material-ui/commit/06667b589952f58ff8c6d277df364ef16dada671/hovercard" href="https://github.com/mui/material-ui/commit/06667b589952f58ff8c6d277df364ef16dada671"><tt>06667b5</tt></a>)</li>
<li>React: 15.1.0</li>
<li>Browser: Chrome (Linux) 51.0.2704.79 (64-bit)</li>
</ul>
<h3 dir="auto">Images &amp; references</h3>
<p dir="auto">Gist with modified code of example (commit see above): <a href="https://gist.github.com/hoschi/21e5fc25646615cf2ac153487f181b8e">https://gist.github.com/hoschi/21e5fc25646615cf2ac153487f181b8e</a></p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/163128/16046468/da95755e-324c-11e6-9c3b-6b46a52ad185.gif"><img src="https://cloud.githubusercontent.com/assets/163128/16046468/da95755e-324c-11e6-9c3b-6b46a52ad185.gif" alt="hover problem - floating action button" data-animated-image="" style="max-width: 100%;"></a></p>
<h3 dir="auto">Problem description</h3>
<p dir="auto">On my mobile devices I touch a FloatingActionButton. In some cases the buttons state is set to hovered. This happens when <a href="https://github.com/callemall/material-ui/blob/master/src/FloatingActionButton/FloatingActionButton.js#L212">handleTouchStart</a> does not get called but only <a href="https://github.com/callemall/material-ui/blob/master/src/FloatingActionButton/FloatingActionButton.js#L222">handleTouchEnd</a>. The button is then hovered because a touch flag is only set in <a href="https://github.com/callemall/material-ui/blob/master/src/FloatingActionButton/FloatingActionButton.js#L214">handleTouchStart</a> but not in <a href="https://github.com/callemall/material-ui/blob/master/src/FloatingActionButton/FloatingActionButton.js#L223">handleTouchEnd</a>.</p>
<p dir="auto">I guess there is no harm in also setting the touch flag to true in handleTouchEnd.</p>
<h3 dir="auto">Steps to reproduce</h3>
<p dir="auto">I couldn't really find the reason why this only happens in one case. I tested it with FloatingActionButtons in other situations and this error didn't occur</p>
<h3 dir="auto">Versions</h3>
<ul dir="auto">
<li>Material-UI: 0.15.4</li>
<li>React: 15.1.0</li>
<li>Browser: Different version of Firefox, Chrome and Safari on mobile devices</li>
</ul>