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 #10612, comment 22

Timestamp:: Sep 9, 2013, 3:56:13 PM (11 years ago)
Author:: Piotrek Koszuliński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #10612, comment 22

initial	v1
1		Regarding t/9764, I think that there won't be a lot of problems. But t/9764 should land on major first, because it is >300 commits long. Then rebasing t/10612 on major won't be so tricky, because it will be just on longer commit and most likely not so much conflicts. t/9764 doesn't touch a lot of browser specific code - most of the changes are architectural.
	1	Regarding t/9764, I think that there won't be a lot of problems. But t/9764 should land on major first, because it is >300 commits long. Then rebasing t/10612 on major won't be so tricky, because it will be just one longer commit and most likely not so much conflicts. t/9764 doesn't touch a lot of browser specific code - most of the changes are architectural.