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 History
Next Change →

Changes between Initial Version and Version 2 of Ticket #11059

Timestamp:: Oct 30, 2013, 2:57:47 PM (10 years ago)
Author:: Piotrek Koszuliński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11059
- Property Status changed from new to confirmed
- Property Version changed from to 4.3 Beta
- Property Component changed from General to UI : Widgets
- Property Summary changed from Widget reinit prcedure to Widget reinitialization procedure should be redesigned

Ticket #11059 – Description

initial	v2
1		Widget reinit/recreate procedure should be rethought.
	1	Widget reinit/recreate procedure should be rethought.
2	2
3		Do we need `cke_widget_new` class anymore?
	3	There's no way currently to reinitialize in a lightweight manner widget to which we lost references. It has to pass through entire process of setting attributes, classes, data, etc. What we need is only - rebinding listeners and initial widget#data.