We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Change
Ticket Comment History
Next Change →

Changes between Initial Version and Version 1 of Ticket #9814, comment 10

Timestamp:: May 7, 2014, 3:18:30 PM (11 years ago)
Author:: Bram
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #9814, comment 10

initial	v1
3	3
4	4	I'm not familiar enough with the CKEditor code base to just dive in and check if the editor uses '''isContentEditable'''. If that is the case I think we have found the origin of this issue.
	5
	6	Update: after some googling if found the following line of code that confirms my suspicion: [https://github.com/ckeditor/ckeditor-dev/blob/master/core/dom/node.js#L727]. The '''isReadOnly''' function will return false for hidden '''contenteditable=true''' elements in chrome. I'm not sure when or where this read only check is called but it guess it's not being called when the visibility of the element changes, causing the element to be stuck in read only mode.