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 #9794, comment 18

Timestamp:: Jun 5, 2013, 7:00:21 AM (12 years ago)
Author:: Piotrek Koszuliński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #9794, comment 18

initial	v1
1		Just a quick check on FF and Chrome and it works fine - it is fired on every key and drag&drop.
	1	Just a quick check on FF and Chrome and it works fine - it is fired on every key and drag&drop (but programatic DOM changes aren't triggering it).
2	2
3	3	In fact, we are planning (but it's hard to tell now if it is going to work) to implement onchange event using undo manager. So this event may not be required for onchange specifically, but to improve undo manager which e.g. has problems with D&D (#7422).