AutoGrow in CKEditor 3?

We'll port the autogrow plugin to version 3 in one of the future releases. We don't expect to have it done for the 3.0.

In any case, the auto grow logic should be quite similar, so a 3.0 plugin should not be that hard to be coded.

I'm also waiting for this good feature. Try to write small code instead but iframe has no id. How to get it from editor instance?

Isn't there a big problem with using an autogrow feature?
If the page is long, and you're at the bottom of your text, the toolbar buttons are off the screen?
Unless do the buttons stay on screen somehow?

Is there an update on this issue? Is AutoGrow present in CKEditor 3? This is a pretty big deal to us, since we would use the AutoGrow feature quite extensively. Thanks for info anyone can provide...

Add 5$ to my account . i can help with autogrow of editor.

Me and joydark implemented it.

Here is the demo: http://rmcreative.ru/playground/ckeditor_autogrow/
Here is the plugin: http://rmcreative.ru/playground/ckedito ... utogrow.js

Sam Dark: thanks for your post. That's exactly what I was looking for.

Is it possible to have AutoGrow work with multiple instances of CKEditor on the same page?

I've never tried it.

This plugin works well with a maxHeight set. I'd like the editor to expand as necessary to fit the entire content. What happens is that when you get to the bottom, the editor expands but the page's scrolling stays where it is and the caret moves on down out of the visible part of the page.
In all, I'd like to use CKEditor 3 in a way that more resembles a normal word editor (OpenOffice) in the following regards:
* toolbar always visible

The overall goal is to make a wiki more easy to edit. So after a user double-clicks any part of the wiki content, CKEditor appears and selects the content that was selected in the normal markup/div, and scrolls that into view. If I could only get the CKEditor to start with the text selected, I guess using the maximize plugin would work fine. (The browser scrollbar would be replaced by the CKEditor iframe's scrollbar, but I guess the user wouldn't mind.)

If readonly worked differently I'd use that, but currently there's no easy way (that I've found) to open links in the top/parent frame. The user can browse the wiki inside the CKEditor, but the URL in the browser isn't updated which kind of defeats the purpose of "navigating a wiki".

I too need autogrow to work with multiple instances on one page. It appears as if this version of autogrow does not work with multiple instances. Only the last instance. Am I doing something wrong?

I found a working solution here:

viewtopic.php?f=11&t=15408&hilit=autogrow

I used the code from the latest post. It resizes both instances of the editor on one page, and with a shared toolbar.

Yipee