<p dir="auto">Chrome wrongly detects input devices, so it enables touchscreen interface. This means that:</p>
<ul dir="auto">
<li>menu is harder to use, as it doesn't detect mousemove</li>
<li>mouse input is broken, it detects all mouse buttons as button 1</li>
<li>selection is broken, a touchscreen selection tool appears</li>
<li>the same problems happen when I use Chrome internal controls, like dev tools</li>
</ul>
<p dir="auto">Bug still happens when I:</p>
<ul dir="auto">
<li>rm -rf ~/.atom ~/.config/Atom ~/.cache/Atom</li>
<li>run atom under a new user account</li>
<li>replace virtual machine graphic cards, change input devices</li>
<li>rebuild from scratch (scripts/clean)</li>
<li>try various chrome flags (--touch-events=disabled, --disable-touch-input, ...)</li>
</ul>
<p dir="auto">Bug doesn't happen when I:</p>
<ul dir="auto">
<li>run atom under a Xephyr X server.</li>
</ul>
<p dir="auto">Bug happens on:</p>
<ul dir="auto">
<li>master</li>
<li>v0.193.0</li>
<li>v0.194.0</li>
<li>v0.195.0</li>
<li>v0.196.0</li>
<li>v0.197.0</li>
<li>v0.198.0</li>
</ul>
<p dir="auto">Bug doesn't happen on:</p>
<ul dir="auto">
<li>v0.188.0</li>
<li>previous versions</li>
</ul>
<p dir="auto">I assume that the problem is due to upgrading to Chrome 21.</p>
<p dir="auto">There is a <a href="https://code.google.com/p/chromium/issues/detail?id=456222" rel="nofollow">known issue</a> with Chrome41 engine running on Linux in VirtualBox. It actually became a show-stopper for Chrome42. <strong>TL;DR</strong>: in VB Chrome41 engine <em>always</em> runs in touch-screen mode, even on desktops.</p>
<p dir="auto">Hotfix in Chrome41 is to pass <code class="notranslate">--touch-devices=123</code> to the chrome command line.</p>
<p dir="auto">Is it possible to pass parameters to Atom’s command line so that chrome engine will understand them?</p>