UserAgent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/51.0.2704.79 Chrome/51.0.2704.79 Safari/537.36

Steps to reproduce the problem:
1. Install an extension with a background script of 250 lines or more.
2. Enable "Collect errors" for the extension on chrome://extensions/
3. Log an error in the background's Console:

  console.error("Oops, an error.");

4. Click "Errors" to see the errors collected for the extension. The code is visible, but the errors are not - the "Errors" box is squashed to nothing.

What is the expected behavior?
Let me ask a question here: Do you want the behaviour I expected to see before I did this myself, or the behaviour I expect _you_ to see if you follow these steps? (I think maybe I've been filling in this box wrong.)

What went wrong?
The "Errors" list (including the "Clear all" link) are reduced to nothing when the code is ~300 lines long. The list should always be tall enough to show the "Clear all" link and at least part of the first error. (And maybe resizeable?)

Did this work before? N/A 

Chrome version: 51.0.2704.79  Channel: stable
OS Version: 
Flash Version: 

Attached is an extension with a 250-line background script which throws two errors. You can see the "Errors" box being squashed, but the script isn't long enough to completely squash it.

Adding

.extension-error-list { min-height: 3.6em; }

to the page style fixes this, more or less, on a 1280x960 display.