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 26

Timestamp:: May 27, 2014, 9:39:07 AM (11 years ago)
Author:: Olek Nowodziński
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #9814, comment 26

initial	v1
1	1	Hum. That's funny: yesterday it seemed to fail on all browsers but today it's indeed just Webkit. So yes, we can restrict that fix to Webkit-based browsers.
2	2
3		As for the support of different cases of `contenteditable` attribute – no, we don't want to do that. Right now, we don't support other cases in our codebase (~25 places) so `isReadOnly` should neither.
	3	As for the support of different cases of `contenteditable` attribute – no, we don't want to do that. Right now, we don't support other cases in our codebase (~25 places) so `isReadOnly` should do neither.