Changes between Initial Version and Version 1 of Ticket #9978, comment 3


Ignore:
Timestamp:
Jun 7, 2017, 12:13:53 PM (2 years ago)
Author:
Jakub Ś
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #9978, comment 3

    initial v1  
    111. Don't compare CKEditor with textarea. Compare it with div having contenteditable="true". This is big difference.
    2 2. Instead of switching to source. Yes CKEditor trims white spaces for example. Instead try looking at the code with dev-tools. Best tool to check is IMO in WEBKIT. (Firebug doesn't do well in live updates)
     2
     32. Instead of switching to source (yes CKEditor trims white spaces), try looking at the code with dev-tools. Best tool to check the soource code is IHMO in Chrome. (Firebug doesn't do well with live updates)
     4
    353. "CKEditor doesn't permit to have a single   between 2 word" - this is browser behaviour. Try it in chrome in contenteditable="true", you’ll see. Type "abc " and you will get abc  in Webkit and Opera. Type def behind it and browser will change it to "abc def".
    46
    5 @remaye this is feature reaquest so please let's not continue this discusson anymore. How space is handled by browsers in contenteditable elements is different story. I have spent few days analysing it and don't want to put all my findings here as this has nothing to do with SHIFT+Space inserting backspace.
     7@remaye this is feature reaquest so please let's not continue this discusson anymore. How space is handled by browsers in contenteditable elements is different story. I have spent some time analysing it and don't want to put all my findings here as this has nothing to do with SHIFT+Space inserting backspace.
© 2003 – 2019 CKSource – Frederico Knabben. All rights reserved. | Terms of use | Privacy policy