This is for any dropdowns in the interfacte (Styles, paragraph, font, size),
The first time it loads, I can click on any of these 4 dropdowns and I can see the content of the dropdown. All next attempts opens a white box instead.
Repro step:
-open ckeditor in a page (mine is in a jquery UI dialog)
- click on any dropdown (for example styles). the styles are shown correctly.
- click on it again. the drop down closes.
- click on any dropdown. Empty white box
Result: the dropdown is empty. further more all other dropdowns shows an empty white box.
Note that there is no js error in console.
EDIT: note that this bug appears ONLY if you click on the dropdown header to close it. If you click on the text area it closes the dropdown without removing everything in it.
What could it be?
Tested on Chrome with CKEditor 4.3 (revision d2184ac)
Uhh... jQ UI dialogs cause a
Uhh... jQ UI dialogs cause a lot of issues all the time. We are planning to make thorough tests to identify problems when running CKEditor in those dialogs and report bugs to jQ UI, but currently we don't know how to fix them. jQ UI does some odd things with events fired outside dialog container and this hack http://bugs.jqueryui.com/ticket/9087#comment:14 was helping for some of them, but I don't know if for this problem too.
Piotrek (Reinmar) Koszuliński
CKEditor JavaScript Developer
--
CKSource - http://cksource.com
--
Follow CKEditor on: Twitter | Facebook | Google+
How do you recommand to show
How do you recommand to show the ckeditor in a popup window?
I am testing the jqWidget window at the moment but I have issues with z-index
Thank you
It's pretty unlikely that the
It's pretty unlikely that the fix in http://bugs.jqueryui.com/ticket/9087#comment:14 was helping anyone, because it can't and never did work. I have gone back and forth a bit with one of the jQuery UI guys and have proposed a seemingly working solution, but we are still trying to confirm if it works everywhere for us. That fix can be seen towards the bottom of http://bugs.jqueryui.com/ticket/9087
The problem this particular user is complaining about is completely unrelated to this particular issue. There are some fixes for that as well (I make note of them at the same link above) but they don't work particularly well under IE. More work to be done there.