When loading the widget as initially parsed in the admin, it takes the width and height of the original textarea, making it often too small. The parsed view takes considerably more space, and will often result in unnecessary scrolling:
This is easily fixable in the js, and I've got a fix ready. But I was wondering if you were set on the current behavior, of it there was a specific reason for how it currently works.
I guess I try to leave default styling where I can, but I agree that it's usually too small. It would be awesome if you put your fix into a pull request!
When loading the widget as initially parsed in the admin, it takes the width and height of the original textarea, making it often too small. The parsed view takes considerably more space, and will often result in unnecessary scrolling:
This is easily fixable in the js, and I've got a fix ready. But I was wondering if you were set on the current behavior, of it there was a specific reason for how it currently works.