Of note, there's an experimental console API that you can use but it requires users to set a flag to use the extension and you wouldn't be able to add it to the chrome store (which I might do at some point).

I ventured into that, but having to set a flag is a deal breaker. Let's hope it becomes official soon.

btw: I just had a chance to look at your implementation. It's definitely going in a different direction than I wanted to take it. I understand the desire to match the default console but I'd like to keep the more powerful editor (along with some other features I'm looking to add).

Great work, though.

I have it set that Cmd+Enter or Shift+Enter runs the code and Enter just creates a normal carriage return. I know this is a little backwards compared to the normal console, so it's definitely possible to switch it around. This just feels natural to me. (Down the road, having app preferences where this can be toggled might be good.)

Ahh yes, just came back here to edit my comment after I found that in the source. I can get used to that.

I'd love to see this become a drop-in replacement for the console. CoffeeScript is so much nicer to deal with in development it's practically the only time I'm still writing plain js.

Read through smacss.com, if you haven't already. It advocates a modular approach that should minimize the impact that components have on other components, thus a style change to one component won't blow up the rest of the site.

Third party tools can be hit and miss. Hopefully you're working with plugins/libraries that don't inject inline code and rely on namespaced classes to achieve the result you need. Then, you have control of the CSS to style as you wish.

(disclaimer: I wrote smacss (but didn't write the blog post))

Exactly. And just because there's a draft specification, doesn't mean browsers will implement it.

Actually, much of what I've detailed came as a result of my work on Yahoo! Mail and Calendar, which is a highly complex web application. Smaller "classic" sites can get away with not having as rigid of a system. Nicole Sullivan's OOCSS covers a bit about this component-based approach and Nicole formerly worked at Yahoo! and has done consulting for Facebook and other companies with large-scale web apps.

If you have any additional categorization that you think would be applicable, however, I'm open to feedback.

Hm, cool. That shuts me up :-)

Guess my underbelly feeling may simply be wrong then :)

I don't believe that SASS saves you from proper organization or naming convention. However, Less and SASS have been mentioned and I'll see about added something that covers how I believe those tools can fit into this (because I believe that can and do).

Yes, very similar to OOCSS. One thing I'd like to do is talk about a number of frameworks and how they fit into these concepts. Nicole has the Facebook example on her web site, I believe.

I'll definitely work on the rest. All of your input is spot on, I think.

Thank you for the very thoughtful feedback.