Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.#1936392: Configure CKEditor's "Advanced Content Filter" (ACF) to match Drupal's text filters settings ensured that ACF was optimally configured: so that it perfectly matches the restrictions by Drupal's text filters.
However, Drupal's text filters need to have the capability to blacklist attributes (filter_html disallows style and on* attributes on all tags). That's why a _ACF_HACK_to_support_blacklisted_attributes function was added to hack in a temporary work-around.
Once http://dev.ckeditor.com/ticket/10202 and http://dev.ckeditor.com/ticket/10276 are fixed, we can remove that hack, and update Internal::generateAllowedContentSetting() to communicate our blacklist to CKEditor in the format that CKEditor decides on.
Comments
Comment #1
Wim LeersComment #1.0
Wim LeersUpdated issue summary.
Comment #2
MustangGB CreditAttribution: MustangGB commentedfredck is asking if http://dev.ckeditor.com/ticket/10202 is still a priority for CKEditor inclusion.
Comment #3
Wim LeersI discussed this with the CKEditor guys already; it needs to be fixed before Drupal 8 is released, but not ASAP. They've adjusted their roadmap accordingly.
This will happen.
Thanks for helping to keep track of things, akamustang :)
Comment #4
catchUntagging. If this is critical, please mark it as such, if it's not, then it doesn't need to be tied to the release.
If it's both critical and not fixed in ckeditor, we'll need to consider whether we want to hold the release up on wysiwyg.
Comment #5
Wim LeersThis does not need to hold up a beta, but it should be fixed before release.
Comment #6
Wim LeersFixed as part of #2039163: Update CKEditor library to 4.4! :)
Comment #7
webchickThat means we don't need to revisit! :)