![Kayce Basques](https://web.dev/images/authors/kaycebasques.jpg) Kayce Basques [X](https://twitter.com/kaycebasques) [GitHub](https://github.com/kaycebasques)

<br />

Hey hey, [Kayce](https://twitter.com/kaycebasques) here, back again for
another digest to update you on what's new in DevTools since last month.

## New features in the Console

In Chrome 56, which is currently in Canary, the DevTools Console is powered by
[CodeMirror](https://codemirror.net/). This enables a whole bunch of new
features, like:

**Syntax highlighting as you type**. Previously, DevTools could only
highlight syntax after a code block had been evaluated.

**Matching parenthesis / bracket / brace highlighting**. If you've got
an extra parenthesis, bracket, or brace, DevTools highlights it red.
![mismatched parenthesis](https://developer.chrome.com/static/blog/devtools-digest-2016-10/image/mismatched-parenthesis-76c3a7f4bd247.png)

Matching parentheses, brackets, or braces are highlighted grey when your
cursor is next to one of them.
![matched parentheses](https://developer.chrome.com/static/blog/devtools-digest-2016-10/image/matched-parentheses-6084ed0e040b6.png)

**Smart return** . When you type out a multi-line code block, DevTools
now knows whether to create a new line or execute your code each time you
press <kbd>Enter</kbd>. For example, suppose you want to
evaluate the following `for` loop in the Console:

```javascript
for (var i = 0; i < 5; i++) {
  console.log(i);
}
```

In the past, hitting <kbd>Enter</kbd> after typing out the first line would
have caused DevTools to evaluate the line, causing an error.
To continue the code block to a new line, you would have had to held
<kbd>Shift</kbd> before pressing <kbd>Enter</kbd>. In contrast, now
DevTools just automatically continues the code block on a new line after
you hit <kbd>Enter</kbd>, as you expect it would.

**Multiple cursors** . Hold <kbd>Command</kbd> (Mac) or
<kbd>Control</kbd>+<kbd>Alt</kbd> (Windows, Linux) and then click.
![multiple cursors](https://developer.chrome.com/static/blog/devtools-digest-2016-10/image/multiple-cursors-427c9adec6967.gif)

## Canary now highlights non-top contexts red

If you've worked in the Console lately, you might have been bitten by a
nasty little bug that was setting the [execution context selector](https://developers.google.com/web/tools/chrome-devtools/console/#execution-context) to values
other than `top`.

That bug should be now be fixed in Stable, but, just to be safe, the DevTools
in Canary (Chrome 56) now warns you that you're not in the `top` context by
highlighting the selector red.
![non-top context highlighted red](https://developer.chrome.com/static/blog/devtools-digest-2016-10/image/non-top-context-highlight-9dae4747bf537.png)

## New user agent: UC Browser

You can now select UC Browser for iOS, Android, or Windows Phone from
the **Network conditions** [drawer tab](https://developers.google.com/web/tools/chrome-devtools/settings#drawer-tabs).
![UC Browser user agent](https://developer.chrome.com/static/blog/devtools-digest-2016-10/image/uc-browser-user-agent-6f990e5892643.png)

## Sharing is caring

As always, we'd love to hear your feedback or ideas on anything DevTools
related.

- Ping us at [ChromeDevTools](https://twitter.com/chromedevtools) on Twitter for brief questions or feedback, or to share new ideas.
- For longer discussions, the [mailing list](https://groups.google.com/forum/#!forum/google-chrome-developer-tools/topics) or [Stack Overflow](http://stackoverflow.com/questions/tagged/google-chrome-devtools) are your best bets.
- For anything docs related, [open an issue](https://github.com/google/WebFundamentals/issues/new) on our docs repo.
- You can always go straight to the team to file a bug or request a feature on [Crbug](https://bugs.chromium.org/p/chromium/issues/list).

Until next month,

Kayce