Changes between Version 1 and Version 2 of Ticket #12199, comment 4
- Timestamp:
- Jun 8, 2017, 10:39:35 AM (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #12199, comment 4
v1 v2 1 You can use API sample to test that. When you type e.g. {{{'test '}}} and then use the {{{Get Editor Contents}}} button then {{{<p>test </p>}}} is returned in Chrome while IEand FF only return {{{<p>test</p>}}}. It is not what is happening in native contenteditable elements where IE returns {{{<p>'test '</p>}}} and FF returns {{{<p>'test '</p>}}} (returns with the help of {{{document.getElementById('wrapper').innerHTML}}}).1 You can use API sample to test that. When you type e.g. {{{'test '}}} and then use the {{{Get Editor Contents}}} button then {{{<p>test </p>}}} is returned in Chrome and Edge while IE11 and FF only return {{{<p>test</p>}}}. It is not what is happening in native contenteditable elements where IE returns {{{<p>'test '</p>}}} and FF returns {{{<p>'test '</p>}}} (returns with the help of {{{document.getElementById('wrapper').innerHTML}}}). 2 2 3 It is also worth mentioning that when you paste the following code into editor source area {{{<p>test </p>}}} and then switch wysiwyg/source, you will get {{{<p>test</p>}}} in all browsers. White space will be trimmed in every browser in this case. 3 It is also worth mentioning that when you paste the following code into editor source area {{{<p>test </p>}}} and then switch wysiwyg/source, you will get {{{<p>test</p>}}} in all browsers. White space will be trimmed in every browser in this case.
