Changes between Initial Version and Version 1 of Ticket #13142, comment 11


Ignore:
Timestamp:
Jul 14, 2015, 12:11:15 PM (4 years ago)
Author:
Piotr Jasiun
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13142, comment 11

    initial v1  
    33I checked the behavior on other browsers and and Chrome removes content completely, but IE 11 keeps `<p>`. These situations are handled later by the `fixDom` method you patched.
    44
    5 However, when I set the `enterMode = CKEDITOR.ENTER_DIV`,run IE 11, create a single paragraph in the editor `<p>foo</p>`, press CTRL+A;Backspace` the `<p>` is properly removed and replaced by `<div>`. The `<p>` is not removed naively so there must be a code in the editor which do it. Moreover when I commented out `fixDom` method `<p>` is still removed. The same code should handle `<div>` and remove it the same way, because this is the same case. We should not create separate fix for it.
     5However, when I set the `enterMode = CKEDITOR.ENTER_DIV`,run IE 11, create a single paragraph in the editor `<p>foo</p>`, press CTRL+A;Backspace the `<p>` is properly removed and replaced by `<div>`. The `<p>` is not removed naively so there must be a code in the editor which do it. Moreover when I commented out `fixDom` method `<p>` is still removed. The same code should handle `<div>` and remove it the same way, because this is the same case. We should not create separate fix for it.
    66
    77Fortunately there is no conflict with `div` plugin, because it automatically add `<p>` inside every `<div>`, event with `autoParagraph = false;` and `enterMode = CKEDITOR.ENTER_DIV`. Do not forget to check if your fix works fine with div-based editor. It should not be a issue, but lets make sure nothing is removed there.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy