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 #9230, comment 2

Timestamp:: Aug 29, 2012, 12:26:44 PM (12 years ago)
Author:: Piotrek Koszuliński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #9230, comment 2

initial	v1
3	3	As I stated before, it's just plain wrong to force save a snapshot on each selection change (we were doing that, just for making the "updateSnapshot" feature work), so the way how it work to update snapshot must be reinvented, at this moment.
4	4
5		Opened t/~~344~~ for the following proposals, which should resolve the issue:
	5	Opened t/9230 for the following proposals, which should resolve the issue:
6	6	1. Published editor.undoManager (required by 2.)
7	7	1. Reworked '''undoManager::update''' to perform a interceptor alike update on undo snapshots, with the DOM modification function passed in (this's not achievable by using event), besides, this method now takes care of detecting the DOM changes, to only amend the stack on demand, thus the '''domChanged''' flag is removed.