title: Has the Chrome console's autocomplete feature gotten more aggressive?
body: <p>It seems like lately I have been having been getting hung up on the auto-completion drop down when using the console in Chrome DevTools. It seems like it has suddenly gotten more aggressive. I have never had a problem with the feature until the other day when I was trying to enter commands into the console quickly in order to test things. I wasn't sure why it wasn't working right. when I'd hit <kbd>Enter</kbd> auto-completion kept popping up and not executing what I typed. At first it seems as if auto-completion was activating whenever I would hit <kbd>Enter</kbd> to execute my code. However, it began to look like it was only popping up when I would end a statement with <code>;</code>.</p>
  <p>For example, typing the following statement into the console and pressing <kbd>Enter</kbd> would not cause the autocomplete drop down to activate:</p>
  <pre><code>console.log('did it')
  </code></pre>
  <p>However, if I add a semicolon then as soon as I press <kbd>;</kbd> a number of milliseconds later the autocompletion feature immediately pops up:</p>
  <pre><code>console.log('did it');
  </code></pre>
  <p>At this point if I press <kbd>Enter</kbd> it will simply select the first entry, <code>$</code>, and add it as the next statement so we get:</p>
  <pre><code>console.log('did it');$
  </code></pre>
  <p><img src="https://i.stack.imgur.com/qI5u0.png" alt="Auto-completion preventing execution" /></p>
  <p>I know this is not really a big deal, after all, the only reason you would need the semicolon is for entering in multiple statements. However, I feel like in the past I've always added a semicolon <code>;</code> to the end of simple single test statements such as the <code>console.log</code> shown above not activated the auto-completion, being able to execute it by just hitting <kbd>Enter</kbd>.</p>
  <p>I definitely feel like <em>my</em> console's auto-completion is being activated more aggressive than it used to.</p>
  <p><strong>Has anyone else felt like the auto-completion in the console is activating too often all of the sudden?</strong> I am wondering whether or not this could have actually been changed in Chrome or if somehow I have made my console start acting this way with a setting or something?</p>
  <p>While writing this I noticed that it seems not to only be after <code>;</code> that auto-completion seems to pop up when it hadn't before. If you refer to <a href="https://developer.chrome.com/docs/devtools/#evaluating_expressions" rel="nofollow noreferrer"><strong>Chrome DevTools - Using the Console</strong></a> you'll see that <strong>auto-completion</strong> is only referred to once:</p>
  <blockquote>
  <p>The Console attempts to evaluate any JavaScript expression you enter at the shell prompt, upon pressing the Return or Enter key. The Console provides <strong>auto-completion</strong> and tab-completion. As you type expressions, property names are automatically suggested. If there are multiple properties with the same prefix, pressing the Tab key cycles through them. Pressing the right arrow key accepts the current suggestion. The current suggestion is also accepted by pressing the Tab key if there is only one matched property.</p>
  </blockquote>
  <p>After this it goes on to say that we can use <kbd>Shift</kbd>+<kbd>Enter</kbd> in order to enter a multi-line expression and it gives the following example:</p>
  <p><a href="https://i.stack.imgur.com/Sm0lo.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Sm0lo.png" alt="ShiftEnterCombo" /></a><br />
  <sub>(source: <a href="https://developers.google.com/chrome-developer-tools/docs/console-files/multiline-expression.png" rel="nofollow noreferrer">google.com</a>)</sub></p>
  <p>This is something I know for sure I have done plenty of times in the past with no problems from auto-completion. When I try to type the code in the above image I get as far as:</p>
  <pre><code>var add = function (val1, val2) {
  </code></pre>
  <p>Then when I press <kbd>Shift</kbd>+<kbd>Enter</kbd> instead of going to a new line like I am positive it did before (for me at least). Apparently anytime a new statement is started it will pop up. <strong>Has anyone else started getting highly annoyed at this feature as of very recently?</strong> Does anyone know if there's a way I could have caused this behavior?</p>