Opened 10 years ago

Closed 10 years ago

#11789 closed Bug (duplicate)

CKEditor inline does not initialize properly in Chrome if the container element is initially hidden

Reported by: Sergey Krilov Owned by:
Priority: Normal Milestone:
Component: General Version: 4.3
Keywords: Cc:


If the editor is inside a container element which is initially hidden, the editor appears disabled and the contents are not editable when you show the container.

The bug is demonstrated in this fiddle:

Note that you can click inside the editor div and the ckeditor toolbar shows up, but all the buttons are grayed out, and you can't actually edit the contents. No JavaScript errors show up in the console.

The issue appears to be Chrome only (tested also in Firefox and IE - both seem to work fine). I'm using Windows 7 (though I'm not sure it makes a difference).

Using CKEDITOR.disableAutoInline does not work either, as demonstrated in this fiddle:

However, it looks like the issue is isolated to the inline editor. This alternative fiddle uses the standard CKEditor, and it works fine in Chrome:

You can easily run into this issue if the editor is inside a jQuery UI tab, or a collapsed panel of any sort. People having been using all sorts of hacks and workarounds for this, including delaying initialization of the editor until the container becomes visible, or destroying/recreating all inline editors. Here are some I found:

Apologies if this is a duplicate. I found some similar issues that are old and probably predate inline editing capabilities (#5956, #6174), but I wasn't able to find anything that's specific to the CKEditor 4 inline editor.

Change History (1)

comment:1 Changed 10 years ago by Jakub Ś

Resolution: duplicate
Status: newclosed

DUP of #9814.

@sergkr I have moved your links to that ticket.

Note: See TracTickets for help on using tickets.
© 2003 – 2022, CKSource sp. z o.o. sp.k. All rights reserved. | Terms of use | Privacy policy