Context Navigation

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

-                      initial
+                      v1
 . Don't compare CKEditor with textarea. Compare it with div having contenteditable="true". This is big difference.
+. 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)
+. 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)
 . "CKEditor doesn't permit to have a single &nbsp; between 2 word" - this is browser behaviour. Try it in chrome in contenteditable="true", you’ll see. Type "abc " and you will get abc&nbsp; in Webkit and Opera. Type def behind it and browser will change it to "abc def".
 @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.
+@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.