i set several paragraphs in ckeditor as below
in the second paragraph, if u select whole line and then use mouse click rather than hot key to un-bold, un-italic etc
(every style that will remove one tag in fact)
the icons state will not be corrected.
* i am using ckeditor 3.5.2
* chrome , ie8, 7 also got the same problem. . .
How can i fix that ?
<div contenteditable="false">
<p>1st paragraph</p>
non-editable text<br />
non-editable text</div>
<p>
problems occur here. . . </p>
in the second paragraph, if u select whole line and then use mouse click rather than hot key to un-bold, un-italic etc
(every style that will remove one tag in fact)
the icons state will not be corrected.
* i am using ckeditor 3.5.2
* chrome , ie8, 7 also got the same problem. . .
How can i fix that ?
Re: div contenteditable + p tag = bugs?
Documentation Manager, CKSource
See CKEditor 5 docs, CKEditor 4 docs, CKEditor 3 docs, CKFinder 3 docs, CKFinder 2 docs for help.
Visit the new CKEditor SDK for samples showcasing editor features to try out and download!
Re: div contenteditable + p tag = bugs?
what is the different between nightly ckeditor and ckeditor3.5.2 ??
I am sure about the bug i said occurs in both IE6,7 and 8 version ,
other browser i am not sure. . .
Re: div contenteditable + p tag = bugs?
Wikipedianot a stable, production-use productused to verify
Documentation Manager, CKSource
See CKEditor 5 docs, CKEditor 4 docs, CKEditor 3 docs, CKFinder 3 docs, CKFinder 2 docs for help.
Visit the new CKEditor SDK for samples showcasing editor features to try out and download!
Re: div contenteditable + p tag = bugs?
so, there is no way to dl the nightly version before 3.5.3 released, right?
Re: div contenteditable + p tag = bugs?
Re: div contenteditable + p tag = bugs?
Attachments:
Documentation Manager, CKSource
See CKEditor 5 docs, CKEditor 4 docs, CKEditor 3 docs, CKFinder 3 docs, CKFinder 2 docs for help.
Visit the new CKEditor SDK for samples showcasing editor features to try out and download!
Re: div contenteditable + p tag = bugs?
so what you are carrying out is that, the icon states problem can solve in nightly version while after switching to the view to source and then back to WYSIWYG mode?
So if i am not going to enable the source view function, I can't solve this problem b4 3.5.3 released?
Or i have to call some functions which work behind the scene when switching the mode from WYSIWYG to Source mode?
Re: div contenteditable + p tag = bugs?
I was able to reproduce the problem described by you (the toolbar icons not showing a correct state) when I turned the style on and off using the mouse and switched from WYSIWYG to Source and back. This did NOT work on the demo page for CKEditor 3.5.2.
The same scenario tested on the nightly build worked so I assume the problem that is causing the issue is now fixed and it will work as expected in CKEditor 3.5.3.
As for the purpose of switching from WYSIWYG to Source and back, I just used it to demonstrate the issue.
Documentation Manager, CKSource
See CKEditor 5 docs, CKEditor 4 docs, CKEditor 3 docs, CKFinder 3 docs, CKFinder 2 docs for help.
Visit the new CKEditor SDK for samples showcasing editor features to try out and download!