Ckeditor update textarea before submit

Export to PDF. Mentions, Tags and Emoji. Find and Replace. Source Code Editing. Multilingual Content. Accessibility Support. Accessibility and Keyboard Shortcuts. Accessibility Checker. Integration Features. Editor Types.

Classic Editor. Inline Editor. Fixed User Interface. Floating User Interface. Shared User Interface. Editor Presets. Standard Preset. Because it is not a string. I need this description on backend file. CKEditor creates a iframe that replaces the textarea, the actual textarea is not used. What you might need to do is update the textarea before submitting. How are we doing? Please help us improve Stack Overflow.

Take our short survey. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more. This is wrong! Because while you waiting for onload of iframe i'm applying my own submit handler on the form and when the time comes, your submit handler will be second after mine. This way your submit handler will be first and textarea contents will be updated before my form serialization and ajax call.

This fixed both 1 and 2 questions. I have downloaded compressed editor. I just wanted to fix your code on my own, but could not find uncompressed editor.

Ofc i could use some kind of js beautifiers, to make it readable, but that's another story Btw why i can't open any issue on your github page?

Have you disabled that option there? I didn't like user first post but I'm writing this so that others could know if they get similar problem. CKEditor 4. Forums CKEditor Support. Last post. Posts: 3. It's really stupid. For example. Why i have to do these manipulations to make it working? Issue2: Why on earth sometimes it's not updating hidden textarea? Yep, performance would suffer. Like GC kicking in every couple of seconds while you type — not really a thing you like.

And you'd still need a listener for submit because you might type text, Tab , Enter to submit very quickly. We'd need a low timeout for the debouncer and hence, affecting performance or a listener for submit. Finally, this is just not a feature which should be on by default.

Stuff like autosave should be opt in — so it should be a plugin. Just got this crazy idea Haha :D Crazy indeed. I'm curious if it would work. The property seems to be proxable:. Whether people want that? I think they would rather like a custom element which behaves properly. Whether they'd like us to modify native elements on the fly I'm not sure. Besides, such a feature requires Proxy so it's not polyfiable.

Therefore, I'd rather see this as an extension, not a core behaviour on which we heavily depend. Although it is possible to override the value property with Object. It seems that the inner HTML of the element is used by the browser instead. So, there is no way to make much magic here, unfortunately, but I've dreamed for a short while :.

Skip to content.