<p dir="auto">Type the entire first line, move to the second line, the text bar starts in front of the first word on the second line and caret is placed at the beginning of the first word.</p>


<ul dir="auto">
<li>[ x] I have searched the <a href="https://github.com/mui-org/material-ui/issues">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Expected Behavior</h2>
<p dir="auto">Caret is placed after the last symbol.</p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">Caret is placed at the beginning of the last word.</p>
<h2 dir="auto">Steps to Reproduce (for bugs)</h2>
<p dir="auto">It is reproducible in some specific environment: cordova + crosswalk project. So I'm sure that it is specific to chromium engine. And I'm going to create a PR to resolve this issue. So hopefully it will be enough.</p>
<h2 dir="auto">Context</h2>

<h2 dir="auto">Your Environment</h2>

<table role="table">
<thead>
<tr>
<th>Tech</th>
<th>Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>Material-UI</td>
<td>0.20.0</td>
</tr>
<tr>
<td>React</td>
<td>16.2.0</td>
</tr>
</tbody>
</table>
<ul class="contains-task-list">
<li class="task-list-item"><input type="checkbox" id="" disabled="" class="task-list-item-checkbox" checked=""> I have searched the <a href="https://github.com/callemall/material-ui/issues">issues</a> of this repository and believe that this is not a duplicate.</li>
</ul>
<h2 dir="auto">Expected Behavior</h2>
<p dir="auto">When I use a Select Field, it should "feel" responsive and fast. Currently, before the menu with all select options pops up, we wait until the mouseclick is over. Instead, at least on non-touch devices we should consider starting the opening animation as soon as the click starts (for instance the mousedown event).</p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">As described in "Expected Behavior", currently we wait until the click event is over before the Select field opens the menu with all options. This makes it feel much less responsive and slow compared with say the native select field in Chrome, which opens instantly.</p>
<h2 dir="auto">Steps to Reproduce</h2>
<p dir="auto">Check the Select page in the current documentation to try it out: <a href="https://material-ui.com/demos/selects/" rel="nofollow">https://material-ui.com/demos/selects/</a></p>
<h2 dir="auto">Context</h2>
<p dir="auto">We use the select field in various places of our app, and we feel like the current behavior of the Select field makes our application feel sluggish and slow.</p>
<h2 dir="auto">Your Environment</h2>
<table role="table">
<thead>
<tr>
<th>Tech</th>
<th>Version</th>
</tr>
</thead>
<tbody>
<tr>
<td>Material-UI</td>
<td>Beta 20</td>
</tr>
<tr>
<td>React</td>
<td>15.6.2</td>
</tr>
<tr>
<td>browser</td>
<td>Google Chrome 61.0.3163.100</td>
</tr>
</tbody>
</table>