We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Change
Ticket Comment History
Next Change →

Changes between Initial Version and Version 1 of Ticket #11545, comment 6

Timestamp:: May 15, 2014, 7:19:52 AM (10 years ago)
Author:: Piotrek Koszuliński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11545, comment 6

initial	v1
1	1	This unfortunately makes sense - the &#8203 is a filling char which is used by CKEditor to workaround Webkit and Blink's bugs.
2	2
3		~~But you haven't explained how are you typing Korean characters. Note that we're using~~ US keyboards and layouts, so this is a bit of unknown field for us. Could you explain how does it work in general and how can we setup our systems to reproduce it?
	3	Could you explain us how do you type Korean characters. We use US keyboards and layouts, so this is a bit of unknown field for us. Could you explain how does it work in general and how can we setup our systems to reproduce it?