<p dir="auto">See screenshot: seems like <code class="notranslate">a/b/file5</code> should appear just below <code class="notranslate">a/file2</code>, not after <code class="notranslate">z/file4</code>.</p>
<p dir="auto"><a target="_blank" rel="noopener noreferrer nofollow" href="https://cloud.githubusercontent.com/assets/3205856/7297018/c295f750-e9bc-11e4-8f48-03fdd4e6717c.png"><img src="https://cloud.githubusercontent.com/assets/3205856/7297018/c295f750-e9bc-11e4-8f48-03fdd4e6717c.png" alt="screen shot 2015-04-23 at 13 28 15" style="max-width: 100%;"></a></p>
<p dir="auto">I'm using OS X 10.9.5, Atom version 0.194.0.</p>
<p dir="auto">Hi all,</p>
<p dir="auto">If I apply the ‘text-rendering: optimizeLegibility’ directive to the stylesheets on .editor or .workspace, any subsequent command palettes, text fields or tabs have a visually broken/erratic caret:</p>
<ul dir="auto">
<li>In text fields, such as the command palette or settings view, the caret appears before the first character even though it's actually pointing to the end of the text;</li>
<li>Moving the caret left and right in an editor tab sometimes causes it to jump several places left and right of where it should be, there doesn't seem to be any discernible pattern and reloading the tab causes different breakages to happen.</li>
</ul>
<p dir="auto">This issue only affects new tabs/palettes created after the stylesheet change occurs, it seems.  Similarly, removing the stylesheet change only takes effect for new tabs/palettes.</p>
<p dir="auto">I'm running Atom HEAD on Gentoo Linux, 64-bit, not using the react editor.</p>
<p dir="auto">Not sure which part of Atom this applies to, so I've filed it against atom/atom (sorry!)</p>