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 #13507, comment 6

Timestamp:: Aug 6, 2015, 10:19:09 PM (9 years ago)
Author:: Sean D Kendle
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #13507, comment 6

initial	v1
2	2	> The FF team responded immediately so there's a chance that this issue will be fixed very soon :).
3	3
4		I'm guessing there hasn't been an update on this? I just spent an hour scouring my code thinking I had messed something up, and updated to the latest CKEditor before I found that this was a known bug. I can confirm that IE and Chrome do, indeed, allow editing of the "editables".
	4	I'm guessing there hasn't been an update on this? I just spent an hour scouring my code thinking I had messed something up, and updated to the latest CKEditor (4.5.2) before I found that this was a known bug. I can confirm that IE and Chrome do, indeed, allow editing of the "editables".
5	5
6	6	What's strange is that I made a quick and dirty test page for a div with "contenteditable=true" and it works fine in FF. I wonder what the difference is?