There is no way to add textarea content

[Artur Formella]

There is no way to change the textarea content in WYSIWYG mode (actually in FF, IE and Opera. In Webkit is buggy).

It should be possible in textarea dialog.

[Alfonso Martínez de Lizarrondo]

#5748 and #5295 have been marked as dups

[Frederico Caldeira Knabben]

Milestone CKEditor 3.x deleted

[Alfonso Martínez de Lizarrondo]

#6113 has been marked as dup

[Alfonso Martínez de Lizarrondo]

Proposed patch

[Alfonso Martínez de Lizarrondo]

The patch rearranges the cols & rows field to use just one row in the dialog and adds a textarea below to set the value.

[Frederico Caldeira Knabben]

The dialog is prety much broken for me, after patch.

[Alfonso Martínez de Lizarrondo]

Increase dialog height

[Frederico Caldeira Knabben]

While the dialog layout is ok/acceptable, I've written some basic dt tests for this in t/3457:
​http://ckeditor.t/dt/plugins/forms/textarea.html

Some tests are not passing.

While the tests may be related to things that are already present in the editor, by introducing the value field it makes too easy to identify the problems, so I think it's a good time to have them fixed as well.

[Frederico Caldeira Knabben]

Sorry, wrong action.

[Frederico Caldeira Knabben]

Ok, I've updated the tests and we have in fact just problems with <textarea> data. The following cases:

<textarea>Line 1
Line 2</textarea>
<textarea>    Spaces before.</textarea>
<textarea>Spaces after.   </textarea>

Both line breaks and extra spaces get lost.

As said earlier, as the field is now available, it's pretty easy to set textarea data and these issues will come to the eyes immediately, especially the line breaks issue. Therefore, better to get it fixed as well.

[Alfonso Martínez de Lizarrondo]

testcase

[Alfonso Martínez de Lizarrondo]

The testcase shows that new lines at the start are respected only by Opera, all the other browsers ignore them. Besides that, IE (tested just 8) also ignores new lines at the end. Fixing those issues seems too complex as it's just the innerHTML property the one that fails there.

The patch adjust the htmlParser\fragment.js to try to respect the whitespace just like done in PREs

[Alfonso Martínez de Lizarrondo]

patch for fragment.js

[Frederico Caldeira Knabben]

Patches 2+3 look pretty good now. All tests passing.

[Alfonso Martínez de Lizarrondo]

Fixed with [7236]