Allow changing height of styles panel

[Grawl]

It's too small, I want to make it a bit higher but don't see resizing cursor on it's top border.

[mauricelam]

Since this is stylesheet only, I don't have a way to make the resize bars work vertically (it requires JavaScript). Currently if you open the bottom console (press Esc), the styles panel will occupy more space. Not very neat, but that's how it works currently.

If you know of a way to work around that, I would be happy to know! :)

[Grawl]

Added two editions that I use for two days. It's better than 70/30 ratio.

[Grawl]

I think this is needed to be an extension, not just custom.css. Extensions can insert custom JS and other cool things.

[mauricelam]

Interesting. I know content scripts does not work with chrome:// urls, so I assume it doesn't work for devtools as well. But this is a really interesting idea and I will look into ways to work around that.

[silentroach]

Maybe this link will be helpful - http://developer.chrome.com/extensions/devtools.html

[mauricelam]

I did some research on the possibility of an extension, and here are my findings

• chrome.devtools API works in an iframe with a different origin, so we cannot access / inject CSS to the built-in devtools.
• Normal extensions cannot get permission to chrome-devtools:// scheme, even with permissions to <all_urls>, so we cannot use content script nor chrome.tabs.executeScript to inject code to the devtools pages.
• There are whitelisted extensions from the Chrome source code. http://code.google.com/searchframe#OAMlx_jo-ck/src/chrome/common/extensions/extension.cc&exact_package=chromium&q=extension::location&l=199 . The comments for "Discover DevTools Companion" seem to imply that accessing devtools is not possible without the superpower of whitelist.
• I tried pretending to be ChromeVox and did get the permission (security hole?). But injecting script using chrome.tabs.executeScript works only if the inspector is in its own window (not docked). Otherwise it throws an "unknown error". I am still looking for where this error comes from.

I will be really interested to know how "Discover DevTools Companion" will script since that is quite exactly what I want. ("Discover DevTools Companion" seems to be a work in progress and is not public yet)