thank you for the feedback. I faced this problem while creation of the component with the release candidates of the 4.1. But, when the final release came out, I noticed that the resize event is fired and I was very glad.

At least, my example should work in all browsers. Maybe, the resize event in 4.1 is fired not in all cases or not in all layouts, or in other words, the bug is not fixed completely.

Due to the link you have give this bug is fixed, however if someone finds the case where the resize event not working, please let me to know, I will try to find the workaround for this case.

The reason is the support of the HTML text modus, that is, the WYSIWYG is not visible, the text is entered directly into the text area. For some reason, when you typing into the text area, the method getValue is called every time you type a character. If I would call ed.save() , it overwrites the newly typed texts with that from the WYSIWYG.

If you do not need the HTML text modus, you can override the method getValue() like this

me.textEditor is a window component.
it seems like the first time setValue is called it is applied directly to the textfield and then loaded by tinymce on first load/show, but the setValue function from Ext.ux.form.TinyMCETextArea which is used on the second change is not working at all

thanks for the bug report. I looks like I have introduced this bug by trying to eliminate the need to call the tinymce.triggerSave(). It was a bad idea. Now, I updated the version 1.3, there this bug is fixed. But, you have again to call tinymce.triggerSave() before getting the value over getValue() or before submission of the form.

thanks for the bug report. I looks like I have introduced this bug by trying to eliminate the need to call the tinymce.triggerSave(). It was a bad idea. Now, I updated the version 1.3, there this bug is fixed. But, you have again to call tinymce.triggerSave() before getting the value over getValue() or before submission of the form.