Closed (fixed)
Project:
CKEditor 4 - WYSIWYG HTML editor
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 Nov 2011 at 02:28 UTC
Updated:
22 May 2014 at 10:40 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dwieeb commentedThe same behavior is occurring with the Token Filter module.
Comment #2
dwieeb commentedIt appears to be fixed in 1.8.
Comment #3
mkesicki commentedComment #4
grasmash commentedThis behavior is still occurring on the latest dev.
Comment #5
grasmash commentedThis problems stems from ckeditor_filter_xss(), which is called when CKEditor is loaded. It gets a list of $format_filters and $security_filters for the input_format, and applies them when the editor is loaded.
This is different from the way that Drupal core is designed to handle input formats. Core's approach is to allow users to input content relatively unmolested (save SQL injection sanitization) and then filter the value upon display. If a user were to re-edit the content, they'd see the original input in the textarea. CKEditor does not follow this approach, and thereby creates a very confusing editor experience.
Take this scenario as an example:
These filters should not be applied when CKEditor loads. A few suggestions for ways to make this configurable:
Comment #6
jcisio commentedComment #8
jcisio commentedCommitted and pushed. Thanks!