<p dir="auto">The Autocomplete demo suggestion container takes up room even when not in use</p>


<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/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">Put two autocompletes above each other (or any other element below an autocomplete) and it will sit flush against the bottom</p>
<h2 dir="auto">Current Behavior</h2>
<p dir="auto">There is around a 200px height gap between autocomplete and the control below</p>
<h2 dir="auto">Steps to Reproduce (for bugs)</h2>
<p dir="auto"><a href="https://codesandbox.io/s/mj5q02oo58" rel="nofollow">https://codesandbox.io/s/mj5q02oo58</a></p>
<ol dir="auto">
<li>Load codesandbox</li>
<li>See two autocompletes</li>
<li>Note that there is a large gap between the two</li>
</ol>
<h2 dir="auto">Context</h2>
<p dir="auto">I fixed it by changing the css. I removed the <code class="notranslate">container</code> key and changed <code class="notranslate">suggestionsContainerOpen</code> to the following.</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="suggestionsContainerOpen: {
    flexGrow: 1,
    position: 'relative',
    minHeight: 200,
    marginTop: theme.spacing.unit,
    marginBottom: theme.spacing.unit * 3,
    left: 0,
    right: 0,
  },"><pre class="notranslate"><code class="notranslate">suggestionsContainerOpen: {
    flexGrow: 1,
    position: 'relative',
    minHeight: 200,
    marginTop: theme.spacing.unit,
    marginBottom: theme.spacing.unit * 3,
    left: 0,
    right: 0,
  },
</code></pre></div>
<p dir="auto">So this is not impacting me. However, your Component Demos are awesome and this caused me some confusion. For future visitors it might be nice to change this behavior.</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>1.0 beta 22</td>
</tr>
</tbody>
</table>
<p dir="auto">I was wondering, if it would be better if we move the <code class="notranslate">selected</code> prop from the <code class="notranslate">MenuItem</code> directly to the <code class="notranslate">ListItem</code>.</p>
<p dir="auto">I was using the <code class="notranslate">Drawer</code> component and I wanted to show the user which <code class="notranslate">ListItem</code> was active in the <code class="notranslate">Drawer</code>. So I thought I make it <code class="notranslate">selected</code>, but than I realized the ListItem has no <code class="notranslate">selected</code> prop, but I remebered that the <code class="notranslate">MenuItem</code> has this prop. I looked into the code and saw that the <code class="notranslate">MenuItem</code> is basicly a <code class="notranslate">ListItem</code>.</p>
<p dir="auto">If we do not think this is a good idea, we should at least tell the user in the docs, when he wants to make a <code class="notranslate">ListItem</code> <code class="notranslate">selected</code> he should use a <code class="notranslate">MenuItem</code> instead.</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>v1.0.0-beta.16</td>
</tr>
</tbody>
</table>