I don't understand this position. This is possible to fix.
TinyMCE does not have this flaw. I use it cross-browser and it works correctly.
Please fix the HtmlEditor so customers can ditch TinyMCE and use ExtJS as a one-stop framework. I like TinyMCE because it works well, and works as advertised, but I want to reduce the footprint of my app by not including ExtJS + JQuery + TinyMCE + misc other libs.
I'm not asking for plugins and custom features, I'm asking for the ability for the editor to work correctly. I paid for the framework with the understanding that it had an HtmlEditor. I am developing the 2nd version of my commercial product, and I need to know that ExtJS takes these shortcomings seriously for its customers' sakes.
The purpose of this feature was to auto-import a template into the editor (triggered by a combox box select event) if and only if the editor content is empty, so as not to overwrite an existing document.
The workaround I've implemented involves simply checking for length < 20 characters. This is good enough, since anything < 20 doesn't indicate significant content.
Please consider my request, though, as there is still good reason for app designers to use TinyMCE and I see no reason why ExtJS cannot beef up its editor by at least one order of magnitude.
I had a look at the tinyMCE code, it seems to occur if you're removing text that doesn't have a root element, so it always inserts one. The code in there is a big ugly hack to take care of it.
Regarding your comments above, we do take bug reports seriously, however comparing the Ext html editor to tinyMCE is apples and oranges. Compared to tinyMCE, there are probably a number of bugs or things that Ext doesn't handle as well as tinyMCE does, but it's not really the intent for this control to be a fully featured html editor.
That isn't to say the behaviour is desireable or correct, but as you can appreciate it's not a major priority to fix such an issue because it's not any kind of show-stopper.
Twitter - @evantrimboli
Don't be afraid of the source code!
>>it's not really the intent for this control to be a fully featured html editor.
Leaving remnants in the content is not in the realm of "fully featured" or even HTML at all. This is intrinsic to a properly functioning editor, regardless of presentation layer.
>>but as you can appreciate it's not a major priority to fix such an issue because it's not any kind of show-stopper.
I "see" it is not a major priority, but I paid $$ so I cannot appreciate it, sorry.
The HtmlEditor has multiple issues. It has a focus issue as well. The forum is riddled with posts regarding replacing the Ext HtmlEditor with a better solution, usually TinyMCE. I think this says something.
I think the definition of show-stopper is relative to the customer. Technically nothing is a show-stopper, if I just choose not to use Ext at all, so lets not talk in terms of show-stopping. The value of your framework is calculated by how many hours saved / spent. If Ext's stance on this is "take it or leave it", I am wondering why I purchased support.