Hi ckeditor team,
Thank you for your excellent work!!
Currently, I've successfully integrated CKEDITOR, GWT and GXT together. However, I find some potential compatible issues between IE and CKEDITOR (work fine in Firefox) and hope you can fix them in the next version.
1. In the "Paste from Word" dialog, the textarea should be focused when I click anywhere in it, but the fact is that it is only focused when I click the first line. The same situation is also happened in the main editor sometimes.
2. Very urgent bug: if I copy and paste the following data to ckeditor from Microsoft Word 2003,
--------ignore this line----
Fd
Sfsd
Fs
Df
Sdf
Sdfsdfsd
Fsd
Fs
Dfsd
F
Sd
-----ignore this line----
and then keep hitting Bold button for 2-3 times or more, then there will be a js error in IE (again, FF works fine), I guess it is caused by those empty lines...the attachment is a screensnap of this situation.
Thank you and hope you can fix them !
Kobe Sun
Thank you for your excellent work!!
Currently, I've successfully integrated CKEDITOR, GWT and GXT together. However, I find some potential compatible issues between IE and CKEDITOR (work fine in Firefox) and hope you can fix them in the next version.
1. In the "Paste from Word" dialog, the textarea should be focused when I click anywhere in it, but the fact is that it is only focused when I click the first line. The same situation is also happened in the main editor sometimes.
2. Very urgent bug: if I copy and paste the following data to ckeditor from Microsoft Word 2003,
--------ignore this line----
Fd
Sfsd
Fs
Df
Sdf
Sdfsdfsd
Fsd
Fs
Dfsd
F
Sd
-----ignore this line----
and then keep hitting Bold button for 2-3 times or more, then there will be a js error in IE (again, FF works fine), I guess it is caused by those empty lines...the attachment is a screensnap of this situation.
Thank you and hope you can fix them !
Kobe Sun
Re: Compatible issue between IE and CKEDITOR?
1. It's an known limitation of IE, we're already have a ticket about it.
2. It would be very helpful if you can open a ticket at our dev site with the MS-Word document attached to help tracking this bug.