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 #12031, comment 3

Timestamp:: May 30, 2014, 6:31:39 AM (10 years ago)
Author:: Urs Wolfer
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #12031, comment 3

initial	v1
2	2
3	3	IMHO, two things should be changed
4		* Add note for that behavior in api docs. I'll do that an create a pull request (PR #103).
	4	* Add note for that behavior in api docs. I'll do that an create a pull request (PR 103).
5	5	* You should get a "change"-event at least when you switches back to wysiwg-mode. Use-case: A save button is disabled by default, it gets activated once there are changes in the editor. The user edits all code in source-mode and switches back to the wysiwyg-mode. The save button is not activated because the change-event is fired only after he does a change in wysiwyg-mode.