I notice some problem with the TinyMCE when I use firefox 4, it's fine if I use IE or Chrome, the scrollbar gets cut when the content in the richtext editor is too long. Please take a look at the attached screenshot. That's taken from TinyMCE website.

I have a set of named bookmarks to different urls in the application (for each user). Is there any way in the 'link' creating dialog of the tinymce form to offer a way to select from one of the bookmarks to populate the link field?

I have a set of named bookmarks to different urls in the application (for each user). Is there any way in the 'link' creating dialog of the tinymce form to offer a way to select from one of the bookmarks to populate the link field?

Some kind of custom work I suppose, if at all possible.

Andy

There's a file browser option to TinyMCE config that lets you specify a function to call. You can use that to open your own Ext style dialog and let the user choose from the bookmarks.

I notice some problem with the TinyMCE when I use firefox 4, it's fine if I use IE or Chrome, the scrollbar gets cut when the content in the richtext editor is too long. Please take a look at the attached screenshot. That's taken from TinyMCE website.

Looks like you have frame: true. You'll need to use anchor: '100% -10' (tweak the -10 to fit proper).

I get that same issue of the bottom of the tinyMCE control being cut off in all browsers...and I'm not using frame: true (or false for that matter).

Looks like the control is being passed the height which it uses to size the text area of the control...before sticking the header bar on which pushes the text box out the bottom of the control.

I had the same issue using TinyMCE 3.4.3.2, Ext.ux.TinyMCE 0.8.5 and Ext 3.2.1.
I figured that in the function '_setEditorSize' in Ext.ux.TinyMCE the Toolbar Element of TinyMCE Editor is not selected therefore the iframe height is not correctly calculated..

replacing line 372-375 in Ext.ux.TinyMCE.js with the following code worked fine for me:

aa0
I agree with you about the semanitcs of the form field. And this is definitely my bug, that I fire event with inner editor. But you also break the semantics, when you wire "keypress" and other such events to Ext "change" event. It is clearly stated that "change" occurs before "blur". And if you want to listen for keyboard events, then wire up to those events explicitly.