This is an old Firefox bug and it has nothing to do with CKEditor as it also appears on a plain contenteditable element. As such, this is something that only the Firefox team is able to fix. Sorry!
I'm working with Amos on this issue and wanted to clarify to make sure we are clear. The issue with the resizing handles being out of alignmnet only occur on the inline version of the editor. When you use the standard editor and insert a table it works fine. You can see this on your demo site in the latest version of Firefox.
Inline editor and classic editor are two different beasts -- classic creates an <iframe> element, to separate itself from the surrounding page, while inline works directly on contenteditable elements on a live page. So the fact that you can only reproduce it in inline and not in classic does not mean it's CKEditor's fault (on the contrary, really). Read our QA's explanation in the bug that I quoted: https://dev.ckeditor.com/ticket/12449#comment:2
This is an old Firefox bug
This is an old Firefox bug and it has nothing to do with CKEditor as it also appears on a plain contenteditable element. As such, this is something that only the Firefox team is able to fix. Sorry!
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!
Anna,
Anna,
I'm working with Amos on this issue and wanted to clarify to make sure we are clear. The issue with the resizing handles being out of alignmnet only occur on the inline version of the editor. When you use the standard editor and insert a table it works fine. You can see this on your demo site in the latest version of Firefox.
Brad
Inline editor and classic
Inline editor and classic editor are two different beasts -- classic creates an <iframe> element, to separate itself from the surrounding page, while inline works directly on contenteditable elements on a live page. So the fact that you can only reproduce it in inline and not in classic does not mean it's CKEditor's fault (on the contrary, really). Read our QA's explanation in the bug that I quoted: https://dev.ckeditor.com/ticket/12449#comment:2
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!