What is the issue with deleting a tab?

I'm definitely interested in exploring the idea of making textareas expand to be large enough to show all of their content. But I'd like to see more work on this before it is incorporated into core. It could be tricky and present problems when using it in the multiple tab page editing interface.

I can't believe I wrote 'tab', how unhelpful.

I actually meant the character, as in \t. Right now in prototype we can use the tab feature to push text forward within our content. What I have noticed is that if you ( 'tab' | \t ) or delete a ( 'tab' | \t ) at a point where the top of the content has been scrolled away, you will be thrown back up to the top of the content.

This can't happen if you have a text box the size of the content, plus it's really easy to see how the code is laid out.

As for content tabs, it shouldn't at all be an issue, all of the navigation and modification of content tabs is done above the text area, so they can all be a variety of different sizes. I did a bit of testing editing the inline styles on a page and they worked fine.

One problem could be the location of the save and create buttons being thrown about the page, but we could always do what Google do in mail and duplicate those actions above the content.

I'll put more effort into coming up with a solution in Prototype.

I second this. The behavior attached to the textarea is so annoying I'd prefer not to have Radiant "help" edit code.

I like the idea of making the textareas autosize. @dirkkelly please feel free to work on this.